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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds useful information beyond those annotations: it explicitly states that 'Reading costs nothing', which is relevant in a price-aware context. It also lists what content will be returned, giving the agent concrete 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?

Two concise sentences, no fluff. The primary purpose is front-loaded in the first sentence, and the second sentence adds the cost-relevant caveat. Every word earns its place.

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 parameterless read-only tool with comprehensive annotations and no output schema, the description fully covers what the agent needs: it names the topics (rules, price, visibility, API links) and the cost implication. Nothing material 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 schema makes parameter semantics moot. The baseline of 4 applies, and the description's mention of the information categories partially compensates for the lack of any query interface.

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 names a specific verb ('Read') and exactly which resources are covered ('Speedbot rules, price, public visibility and API links'). This clearly distinguishes it from the many sibling tools that perform actions or retrieve other data.

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 this is the entry-point for understanding Speedbot's rules, pricing, visibility, and API links, giving clear context for when it is appropriate. It does not explicitly rule out alternatives, but among dozens of specialized siblings, the scoped resource list effectively guides selection.

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