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

With no annotations provided, the description carries the full burden. It discloses useful behavioral traits: it is free, served locally, and involves no upstream call, which helps the agent understand cost and latency. However, it does not state whether it is read-only, idempotent, or what the output format looks like, leaving some gaps.

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 a single, front-loaded sentence that conveys the key points: free, complete tool/price table, local, and no upstream call. Every phrase earns its place and there is no wasted text.

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 the tool's simplicity (zero parameters, no output schema, no annotations), the description provides enough context to understand its purpose and key operational characteristics. It could be improved by briefly describing the structure of the price table (e.g., what 'price' means in this context), but it is largely complete.

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 takes zero parameters, so the baseline score is 4. The description does not need to explain parameter usage, and it appropriately focuses on what the tool returns rather than how to invoke it.

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 states a specific resource: the complete tool/price table for the MCP gateway. It distinguishes itself from sibling tools by clarifying that it is about this gateway's own pricing (served locally), not token or market prices. However, it lacks an explicit verb, so it is slightly less than a perfect 5.

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 usage by noting it is 'Free' and 'served locally, no upstream call,' suggesting the agent should use it when it needs the gateway's tool/price information without incurring network cost. It does not explicitly say when to use this versus alternatives, but the context is clear enough for an implied guidance rating.

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