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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is set. The description adds behavioral context by stating it is free and enumerating the specific metrics it returns (feed health, snipe-tax facts, etc.), which goes beyond what annotations provide. It doesn't contradict annotations, and it provides useful context about what the agent can expect.

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 brief (two sentences) and front-loaded with 'Free' to immediately convey cost. It packs the purpose and key metrics into the first sentence, and the second sentence gives usage guidance and a sibling alternative. No filler; every word contributes to understanding.

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 there are no parameters, no output schema, and the annotations cover safety, the description is fully sufficient for an agent to decide when and how to call this tool. It explains what metrics are provided, clarifies its scope, and routes to the sibling for per-curve needs. Nothing essential is missing.

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 tool has zero parameters, so the description's explicit statement 'No arguments' reinforces that there is nothing to configure. With a 100% schema coverage (empty schema) and no parameters, the description adds value by confirming the absence of parameters, which is helpful for an agent deciding whether to call it. Since there are no parameters to explain, a baseline of 4 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 explicitly states it is a 'pons regime meter' for Robinhood Chain and lists the specific metrics it provides (launches per hour, graduations per hour, median launch-to-graduation seconds, etc.). It clearly indicates the resource (chain 4663) and the action (gauging launch activity), and it distinguishes itself from the sibling rhc_curve_card by emphasizing whole-chain scope.

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 explicitly says to use it to gauge Robinhood Chain launch activity as a whole, and explicitly tells the agent not to use it for one curve, pointing to rhc_curve_card instead. This gives clear when-to-use and when-not-to-use guidance, along with an alternative tool.

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