get-athlete-shoes

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

With no annotations, the description must carry the burden of behavioral disclosure. It states the tool 'fetches' (implying read-only) and notes 'authenticated athlete', which hints at auth requirements. However, it does not disclose potential side effects, rate limits, or any required OAuth scopes, leaving some ambiguity for a simple read operation.

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, focused sentence with a clear verb-first structure and no unnecessary words. It front-loads the key information about the resource and included data.

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 zero-parameter read tool with no output schema, the description covers the essential context: it names the resource, the auth scope, and the key returned fields (usage distance, primary flag). It could list all return fields, but 'including' suggests additional data is present, which is acceptable for this simple tool.

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 and the schema has no properties, so the baseline is 4. The description appropriately focuses on what the tool returns rather than parameter syntax, which is unnecessary here.

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 ('Fetches') and identifies the resource ('athlete's shoes'), clearly distinguishing it from sibling tools like get-athlete-stats or get-athlete-profile. It also scopes to the authenticated user and mentions key fields returned.

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?

No guidance is given on when to use this tool versus alternatives. It describes what the tool does but lacks any contextual 'when' or 'when not' scenarios, such as comparing with activity or profile tools.

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