my_tool_report

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

The description transparently discloses that the data is user-reported, not measured by HyperRoute, and that the tool should not claim the user's tool is worse. It also mentions the related update action, providing clear behavioral expectations.

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 with the core purpose first, followed by usage context and important caveats. It is slightly verbose due to repeated emphasis on 'user's own reports', but remains clear and focused.

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 description fully covers what the tool does, when to use it, the nature of the data, and the follow-up action (update_my_tool). It provides sufficient context for an agent to decide when and how to invoke it correctly.

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 has zero parameters, and the description does not need to explain any. The schema is fully covered, and there is no missing parameter information to add.

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 that the tool reports the user's own track record on declared tools, per capability region, including alternatives. It also distinguishes this from HyperRoute measurements, making its purpose unambiguous.

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 states when to deliver the report: when the user asks how their tools are doing, or when a declared tool repeatedly underdelivers. It also provides actionable guidance on what to relay and what to avoid.

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