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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds value by specifying the record contents and the conditional nature of the sponsored link ('when available'). It does not mention 404 or error behavior, but for a read-only get tool this is a minor gap.

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, dense sentence that front-loads the core action and then lists specifics. Every phrase earns its place, including the caveat 'when available.' There is no fluff or repetition.

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 simple get-by-slug tool with one parameter and no output schema, the description explains what will be returned (scores, metrics, citations, link) and includes the conditional link. It would be more complete with a mention of not-found behavior, but overall it covers the essential context well.

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 a single 'slug' parameter with zero description coverage, and the description does not explicitly explain how to use 'slug'. Saying 'one exact public paddle record' lightly implies slug identifies the record, but the description does not clarify slug format, requiredness, or how it maps to the record. With 0% schema coverage, the description should compensate more than it does.

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 uses a specific verb ('Get') and resource ('one exact public paddle record'), clearly distinguishing it from siblings like search_paddles and compare_paddles. It also enumerates what is returned (scores, metrics, citations, sponsored link), making the tool's purpose unmistakable.

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 phrase 'one exact public paddle record' implies this tool is for exact slug-based lookups, but it does not explicitly state when to use it versus search_paddles or compare_paddles. There is no direct alternative guidance or exclusionary language, so the usage context is only implied.

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