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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the score is specifically 'after FACT slashing', the output is JSON with score and trust level, and there is a cost of $0.01 per call. It does not contradict annotations. It could have disclosed rate limits or whether the score is cached, but the added context is meaningful.

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 sentences with zero waste. The core action and output are front-loaded, followed by compliance and cost details. Every sentence earns its place, and the description is compact enough to be parsed quickly by an agent.

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 single-parameter read-only tool with a full output schema and complete schema coverage, the description is nearly complete. It covers what the tool returns, the context (FACT slashing), compliance, and cost. The only minor gap is that it doesn't describe error conditions or rate limits, but these are not essential for a simple read operation with annotations already covering safety.

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%, so the schema already fully documents the single parameter (agent_did). The description adds the context that the score is an IATP reputation trust score after FACT slashing, which reinforces the parameter's purpose, but it does not add new syntax or format details beyond the schema. 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?

The description states a specific verb ('Retrieve'), a specific resource ('an agent's IATP reputation trust score'), and a precise scope ('after FACT slashing'). It also names the output format ('JSON score and trust level') and the score range (0-10), which distinguishes it from sibling tools like verify_agent_trust or get_agent_maturity. The title and description align, and the tool's purpose is immediately clear.

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 implies when to use this tool: when you need an agent's IATP reputation trust score after FACT slashing. It also lists compliance frameworks (EU AI Act Art. 14, KYA-OS, IETF AID) and cost, which gives context for selection. However, it does not explicitly state when NOT to use it or name alternatives like verify_agent_trust, so it falls short of a 5.

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