notion_get_block

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

The description mentions routing details (JWT, tenant, company scope) but fails to disclose whether the operation is read-only, what side effects exist, or what the response contains. With no annotations, this lack of behavioral context is a significant gap.

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 short but includes irrelevant routing info that does not aid tool selection. It could be more concise and front-loaded with the actual purpose and usage.

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?

Given the single parameter with no schema description and no behavioral details, the description is incomplete. Although an output schema exists, the agent lacks essential context to correctly invoke the tool (e.g., what inputs to provide).

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?

The description states that 'arguments' is a JSON string for the connector operation but does not specify what keys or values are expected. With 0% schema description coverage, the description should compensate, but it only adds minimal meaning beyond the schema.

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 states 'get_block' as a Notion connector operation, but it does not clarify what a block is in Notion context or distinguish it from similar notions like notion_get_page or notion_get_comment. The purpose is partially clear but lacks specificity.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it, leaving the agent without decision support.

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