add_page_preview_block

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

No annotations are provided, so the description carries the full burden. It mentions 'prevent rich snippets,' hinting at a functional outcome, but fails to disclose critical behavioral traits such as required permissions, whether this is a mutating operation, potential side effects, or rate limits. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence with zero waste. It is appropriately sized and front-loaded, making it easy to parse without unnecessary elaboration.

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 complexity of a mutating tool with 3 parameters, 0% schema coverage, no annotations, and an output schema (which reduces the need to explain returns), the description is incomplete. It lacks details on parameter semantics, behavioral context, and usage guidelines, making it insufficient for effective tool selection and invocation.

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 description coverage is 0%, so the description must compensate. It adds no meaning beyond the input schema, not explaining what 'site_url,' 'block_url,' or 'block_type' represent, their formats, or how they interact. With 3 parameters and no schema descriptions, this is inadequate.

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 the tool's purpose as 'Add a page preview block to prevent rich snippets,' which provides a clear verb ('Add') and resource ('page preview block'). However, it doesn't differentiate from siblings like 'add_deep_link_block' or 'remove_page_preview_block,' leaving the specific role of this tool within the family ambiguous.

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. With siblings like 'add_deep_link_block' and 'remove_page_preview_block,' the description lacks context on appropriate scenarios, prerequisites, or exclusions, offering minimal usage direction.

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