get_collection

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 includes a notable behavioral instruction—not to fabricate data on failure—which is valuable for agent behavior. However, it lacks disclosure of read-only status, authentication needs, rate limits, or error response format. The warning prevents hallucination but does not comprehensively describe the tool's behavior.

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 one clear sentence plus a warning—short, front-loaded, and no redundant information. Every part earns its place.

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 single-item retrieval tool with two parameters and no output schema, the description covers the core purpose and provides a critical behavioral warning. It does not detail the return values (basic vs consolidated), common errors, or when to prefer basic over consolidated. Overall, fairly complete but could benefit from a brief output summary.

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 description coverage is 100%, so both parameters are already documented. The description only echoes the optional consolidated flag ('optionally with consolidated data') without adding new meaning or usage details. Baseline 3 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 the tool retrieves details for a specific collection/payment, with optional consolidated data. This distinguishes it from sibling tools like list_collections (which returns multiple items) and get_invoice (different entity).

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 explicit when-to-use or when-not-to-use guidance is given, nor are alternatives mentioned. However, from the tool name and sibling context, its intended use (getting a single collection) is implied. A clearer statement like 'Use this instead of list_collections when you have a specific collection_id' would raise this score.

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