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

With no annotations, the description carries the full burden. It discloses that it returns live missions with specific fields (organization, commitment, places left, minor eligibility, signup URL, association link), and notes that coverage is non-exhaustive and limited to JeVeuxAider. It does not mention rate limits or auth, but the read-only nature is implied adequately.

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 four sentences that are front-loaded with the core purpose and then provide supplementary details. Every sentence adds value with no redundancy, though it could be slightly tightened.

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?

Given 6 parameters, no output schema, and no annotations, the description covers tool purpose, usage context, parameter roles, return fields, and coverage scope. It adequately equips the agent to decide when and how to use the 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%, but the description adds value by clarifying parameter meanings: e.g., location is a French city or 5-digit postal code, query includes example keywords, and remote implies location is ignored. This enriches understanding beyond the schema alone.

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 it finds open volunteering missions near a French city or postal code from the official platform JeVeuxAider.gouv.fr. It specifies the verb 'find' and the resource 'volunteering missions', and distinguishes from searching for associations in general, leaving no ambiguity.

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 states 'Use this when someone wants to BE a volunteer (donner de son temps), not when searching for an association in general.' It also notes coverage limitations (JeVeuxAider missions only). While it doesn't name sibling tools, the context is clear enough to guide appropriate use.

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