get-block-by-id

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states a read action ('Find') without mentioning response format, error behavior, authorization requirements, or the meaning of the includes parameter, leaving significant behavioral unknowns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundant words. It directly states the tool's purpose and is appropriately sized for a straightforward lookup operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimally viable for a simple get-by-id operation, but it leaves the optional includes parameter unexamined and provides no information about the return shape. Given no output schema and no annotations, the description is adequate but has clear gaps around optional behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the blockID parameter is adequately described as 'ID of block to return'. The description adds little beyond reinforcing the key parameter, and the vague 'includes parameter' schema text is not clarified, but the required parameter is clear enough for basic invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Find' and the resource 'block by its ID', making the operation unambiguous. It naturally differentiates from sibling tools like get-page-by-id, get-file-by-id, and get-user-by-id by naming the exact entity type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage context or alternative tool guidance is provided. The description does not mention when to prefer this tool over get_page_content or get-child-pages, nor does it explain any prerequisites or when the optional includes parameter should be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.