get_donation

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. 'Obtenir' implies a read-only operation, but the description adds no context about authentication requirements, error behavior, return format, or side effects. Minimal transparency beyond the inferred read operation.

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 a single, succinct sentence that directly conveys the tool's action. It is front-loaded with the key information and contains no extraneous 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?

For a simple one-parameter retrieval tool, the description covers the basic purpose. However, with no output schema and no parameter details, it lacks information about the returned object structure or potential edge cases. It is adequate but leaves room for more helpful context.

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 schema has one parameter 'id' (number) with zero description coverage. The tool description does not clarify that 'id' refers to the donation ID or provide any additional meaning. The agent must infer the parameter's purpose from the tool name and naming conventions, which the description does not compensate for.

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 'Obtenir les détails d'un don' uses a specific verb (obtenir) and resource (détails d'un don), clearly indicating retrieval of donation details. It implicitly distinguishes from siblings like list_donations and create_donation by focusing on a single donation, though it doesn't explicitly name alternatives.

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 provides no guidance on when to use this tool versus alternatives such as list_donations or create_donation. It only states what the tool does, without any context about prerequisites, exclusions, or scenarios for use.

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