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

Beyond the annotations, which already declare destructiveHint=true and idempotentHint=false, the description adds meaningful behavioral context: an ownership permission requirement and an important side effect (active subscriptions are cancelled automatically). This helps the agent anticipate consequences beyond a simple delete call.

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?

Three short sentences deliver the essential information without wasted words. The primary action is stated first, followed by the permission constraint and the most consequential side effect.

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 simple single-parameter delete operation with a full output schema and robust annotations, the description covers the key non-obvious details: ownership requirement and automatic subscription cancellation. Nothing critical is missing for an agent to invoke this safely and 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 100% for the single blogId parameter, and the description's 'by ID' matches the schema. The description does not add additional parameter-level detail beyond what the schema already provides, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Delete a blog by ID') and clearly distinguishes this tool from sibling delete operations for other resource types like delete_collection and delete_page. The action and target are unambiguous.

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?

Clearly establishes a prerequisite ('Only the blog owner can delete') and identifies the operation's scope. It does not explicitly discuss when not to use the tool or enumerate alternatives, but the blog-specific naming and context make the intended use clear.

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