get_fingerprint

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

With no annotations, the description discloses error condition (if no fingerprint generated) and return contents (archetype, scores, tags, metadata). Does not explicitly state read-only nature, but it's implied for a retrieval tool.

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 sentences with no wasted words. Purpose is front-loaded, and additional details are efficiently packed.

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 output schema exists, the description adequately covers key return elements and error condition. The tool complexity is low (single parameter, read operation), and the description meets all needs.

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 coverage is 100% for the single parameter league_id. The description does not add semantics beyond the schema's description of 'UUID of the league', so baseline score applies.

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 clearly states it retrieves an existing fingerprint profile for a league, specifies return elements (archetype classification, dimensional scores, etc.), and distinguishes from sibling tools like generate_fingerprint which creates the fingerprint.

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?

Explicitly advises using generate_fingerprint first if no fingerprint exists, providing clear context. Does not explicitly exclude other siblings, but the error condition serves as usage guidance.

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