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

Annotations already provide readOnlyHint=true and idempotentHint=true, establishing the tool as safe and idempotent. The description adds value beyond this by disclosing that it is free (no API key/credits) and explaining the scoring mechanism ('high Hive contributions → LEGENDARY/MYTHIC tier'). It does not contradict 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 well-structured: purpose, return fields, use-case, scoring rationale, cost, and return shape. However, 'FREE' is mentioned twice, which is slightly redundant. Otherwise, every sentence earns its place, keeping it compact enough for the information delivered.

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?

This is a simple one-parameter, read-only lookup tool with no output schema. The description compensates by listing the exact return fields ({found, trust_score, tier, tier_description, public_stats, actions}) and even enumerating possible tier values. It also covers the 'when to use' context, making it complete for its complexity.

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 covers 100% of the single parameter (agent_id) with a clear description including how to find the ID. The tool description does not add any additional parameter-level semantics beyond the schema, so the baseline of 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 clearly states the tool's purpose: a 'free trust oracle for any agent' that returns a trust score and tier. It is specific about the resource (agent reputation) and the action (returns score/tier), and it distinguishes itself from sibling tools by explicitly tying its use to agent_ping and swarm_broadcast decisions.

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 gives explicit when-to-use guidance: 'Use before trusting an agent_ping or swarm_broadcast.' It also highlights the free cost as a reason to prefer this tool. However, it does not mention when-not-to-use or provide alternative tools, so it lacks the full exclusion/alternative context needed for a 5.

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