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

The description outlines the tool's behavior: it fetches the card, verifies signatures, scores supply-chain risk, folds in threat intel, and returns a verdict (allow/review/deny) along with resolved identity, capabilities, and auth. There is no contradiction with annotations (readOnlyHint=false indicates possible mutation, but the description does not mention side effects, which is acceptable for a verification tool). It adds context beyond annotations.

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 concise and front-loaded with the core purpose. It includes necessary details without excessive verbosity. However, it could be slightly more structured (e.g., using bullet points) for clarity.

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 absence of output schema and low schema coverage, the description provides a good overview of inputs, process, and outputs. It explains the verdict types and the resolved identity, capabilities, and auth. Missing are error conditions or what happens with invalid cards, but overall it is sufficient for an AI agent.

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 description adds meaningful context to the parameters: it explains that 'url' is for AxioRank to fetch the card and 'document' is for inline input. It also lists supported protocols, although it does not detail each one. With 0% schema coverage, this description compensates well.

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 tool's purpose: to verify an identity card (A2A Agent Card, MCP server card, etc.) before connecting. It specifies the action ('vet'), the resource ('identity card'), and distinguishes it from sibling tools as a preflight verification step.

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 explicitly says 'BEFORE connecting to it' and instructs the agent to supply either a URL or an inline document. It also mentions the required scope. However, it does not explicitly state when not to use this tool or provide alternative tools for similar tasks, which would be helpful.

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