get_fingerprint

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

No annotations are provided, so the description carries the full burden. It states the tool is 'heavy' and returns full channels and timeline, indicating large payload. This adds behavioral context beyond the schema, though it does not disclose auth or rate limits.

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 two sentences: the first defines purpose, the second gives usage guidance. Every word adds value with no redundancy or fluff.

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-ID tool with one parameter and no output schema, the description is largely complete. It explains when to use and what data it returns. It could mention the absence of filtering or pagination, but the 'full payload' hint suffices.

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 one required string parameter 'id' with 0% description coverage. The description does not elaborate on the id parameter beyond its role in identifying the fingerprint. With a single parameter and clear purpose, it partially compensates but lacks format or constraints.

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 the tool pulls a single neural fingerprint by ID with full channels and timeline data, using a specific verb and resource. It distinguishes itself from siblings like list_fingerprints (which lists) and compare_fingerprints (which compares).

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 includes 'Heavy — only call when you need the full payload,' giving clear context on when to use (for full data) and implicitly when not to (if a summary suffices). It does not explicitly name alternatives but the warning provides guidance.

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