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

With no annotations provided, the description carries the full burden. It correctly indicates a read operation ('get') and adds useful context ('full record', 'by Bar number id or name'), but it does not disclose behavior when both parameters are supplied, when neither is provided, or error/return behavior. For a simple read tool, this is adequately transparent but not rich.

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?

A single sentence, eleven words, front-loaded with the verb. No wasted words; every part is relevant. It is efficient and appropriately sized for a simple lookup tool.

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 tool has no output schema, no annotations, and no required parameters. The description explains the core purpose and lookup methods, but lacks details about return shape, what 'full' includes, or failure modes. Given the simplicity, it is somewhat adequate but leaves gaps for an agent to infer.

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?

Schema description coverage is 0%, so the description must add meaning. It clarifies that 'id' refers to a Bar number and 'name' refers to the defender's name, and implies these are alternative lookup keys. However, it does not specify format, exact vs partial matching, or precedence when both are given.

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') with a clear resource ('full defender record') and explicitly states lookup keys ('Bar number id or name'). This distinguishes it from sibling like search_defenders, which likely returns partial results, and other role-specific get tools.

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 implies usage when you have a Bar number or name and need the full record, but it does not explicitly say when to avoid this tool or use alternatives like search_defenders. No exclusions or alternative tools are mentioned.

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