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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds value by noting it's FREE (no API key or credits) and detailing the return structure. The 'virtuous cycle' explanation adds context about ecosystem dynamics without contradicting 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 informative yet compact, covering purpose, usage, return format, and cost in a few sentences. The 'virtuous cycle' sentence is slightly promotional but not redundant, making it efficient without being overly verbose.

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?

With only 1 parameter, full schema coverage, and read-only annotations, the description provides all necessary context: what it does, when to use it, what it returns, and access requirements. It is complete for a simple look-up tool.

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 schema already provides 100% coverage for the single parameter, including where to find agent IDs (leaderboard or agent_ping). The description does not add new parameter-specific semantics beyond the schema, so the 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 clearly identifies the tool as a 'trust oracle' that returns a trust score, tier, and other agent metrics, with a specific verb and resource. It also distinguishes itself from siblings by explicitly mentioning its use case: 'Use before trusting an agent_ping or swarm_broadcast.'

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 provides explicit context on when to use the tool: 'Use before trusting an agent_ping or swarm_broadcast.' It does not name alternative tools or explicitly state when not to use it, but the use case is clear and actionable.

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