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

The annotations already indicate readOnly, idempotent, openWorld, and non-destructive. The description adds a useful behavioral nuance beyond those flags: 'Live evidence only; unknown stays unknown.' This tells the agent the tool does not fall back to stale data or fabricate a result, which is valuable behavioral context for a verification tool.

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 short sentences carry the full meaning with no filler. The primary instruction is front-loaded, and the behavioral constraint ('Live evidence only; unknown stays unknown') is tightly packed and memorable.

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?

The tool is simple and its annotations cover safety and world semantics, but with no output schema and no parameter documentation, the description should explain what the result looks like or what 'verify' returns. The 'unknown stays unknown' line hints at the outcome, but the agent still lacks a clear picture of the return value and target format.

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 input schema only has one parameter, target, but schema description coverage is 0% and the description does not explain what 'target' should contain (e.g., an address, ID, URL, or name). The tool name and description imply provider identification, but the agent is left to guess the exact format and semantics.

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 a specific action ('verify') and a resource ('a provider'), and adds a timing constraint ('before using it'). It does not explicitly name or contrast sibling tools, so it misses the top tier for sibling differentiation, but the purpose is unmistakable.

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?

'Verify a provider before using it' gives an explicit context for when to call this tool. It does not enumerate when not to use it or name alternatives like check_history or check_status, but the 'before using it' guidance is a clear enough trigger for an agent.

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