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

With no annotations, description carries full burden. Discloses that payment proof grants full access; without it, returns a strategic excerpt and challenge. This is good transparency for a read-only tool, though no mention of side effects, rate limits, or auth details beyond payment.

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 concise sentences front-loading the main purpose and then critical usage condition. No fluff; every sentence adds value.

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?

Covers core behavior including payment proof implications. Output schema likely details return format, so not needed here. Missing any mention of how to handle errors or limits, but overall sufficient for a focused read 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?

Schema coverage is 100%, so baseline is 3. The description adds context about payment proof behavior but does not elaborate on parameter syntax or constraints beyond what schema already provides. No additional value for slug parameter.

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?

Clearly states it reads pure text contents of a specific dossier. However, does not differentiate from siblings like get_dossier_delta or ask_intelligence_rag, which could cause confusion about which tool to use for similar tasks.

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 describes when payment proof is required and what happens without it. Provides context for choosing this tool for full text or partial excerpt. Could be improved by mentioning when not to use it (e.g., for filtered or delta queries).

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