remove_page_preview_block

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states the action 'Remove' without explaining what 'remove' entails - whether it's permanent, reversible, requires specific permissions, has side effects, or what happens to associated data. This is inadequate for a mutation tool with zero annotation coverage.

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 that states the core action without unnecessary words. It's appropriately sized for a simple removal operation and front-loads the essential information.

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?

For a mutation tool with no annotations, 0% schema coverage, and 2 required parameters, the description is insufficient. While an output schema exists (which reduces the need to describe return values), the description doesn't address behavioral aspects, parameter meanings, or usage context that would help an agent understand when and how to invoke this tool correctly.

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 both parameters are undocumented in the schema. The description provides no information about what 'site_url' and 'block_url' represent, their format, or how they identify the specific page preview block to remove. The description fails to compensate for the complete lack of schema documentation.

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 clearly states the verb 'Remove' and the resource 'page preview block', making the purpose immediately understandable. It's specific about what action is performed, though it doesn't explicitly differentiate from sibling tools like 'remove_deep_link_block' or 'remove_blocked_url' which have similar removal patterns.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when removal is appropriate, or what distinguishes it from other removal tools like 'remove_blocked_url' or 'remove_deep_link_block' in the sibling list.

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