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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds critical behavioral context beyond annotations: the public share link remains active after removal, and unshare_verification is needed to revoke it. It doesn't describe auth or rate limits, but for a simple mutation the side-effect disclosure is valuable.

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?

Two sentences with zero waste. The primary action is front-loaded, and the important caveat about the share link follows immediately. Every sentence earns its place.

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 a simple removal tool with an output schema, full parameter documentation, and annotations covering safety, the description supplies the key missing side-effect information (share link persistence). It could be slightly more complete by noting what happens to the verification itself or portfolio ordering, but it covers the essential behavioral surprise.

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?

There is one parameter, verification_id, with 100% schema description coverage. The schema already explains that it is a UUID returned by verify_photo, verify_content_credentials, or list_verifications. The description adds no further parameter semantics, which is acceptable given the high coverage – baseline 3 applies.

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 a specific verb and resource: 'Remove a verification from the portfolio.' It distinguishes the action from portfolio-level deletion and hints at a related sibling (unshare_verification), though it doesn't explicitly contrast with all siblings like update_portfolio_item or delete_portfolio.

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?

It gives clear guidance on when to use this tool and a conditional follow-up: call unshare_verification if the share link should be made private. However, it does not explicitly state when not to use this tool or name alternatives beyond unshare_verification.

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