list_fingerprints

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

Without annotations, the description carries full burden. It discloses that the tool returns only metadata and hints at data source for brand_id from list_brands. However, it does not mention permissions, rate limits, or other behaviors like sorting or pagination.

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 efficiently convey purpose, filtering, and distinction from a sibling tool. No wasted words.

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?

A list tool with 3 parameters and no output schema. Description covers basic purpose and filtering, but lacks details on pagination (limit behavior), ordering, and return format. Could be more complete for a list operation.

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 only 33% (brand_id). Description adds cross-reference for brand_id, but does not explain label enum values or provide details about limit beyond its default. Given low coverage, more parameter explanation is needed.

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 verb 'List' and the resource 'TRIBE neural fingerprints'. It distinguishes from sibling 'get_fingerprint' by noting this returns metadata only, and also mentions filtering options, making the purpose unambiguous.

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?

Provides explicit context by stating that this tool returns metadata only and advises using 'get_fingerprint' for full data. However, it does not address when to use alternatives like 'compare_fingerprints' or mention any prerequisites or when not to use.

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