Rechercher des drapeaux

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description has lower burden. It adds pagination behavior (defaults, max) but doesn't disclose additional traits like authentication needs or rate limits.

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 concise with a clear structure: purpose sentence, Args list, Returns. It is front-loaded and each part is relevant. Slight redundancy with schema but minimal waste.

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 search tool with 3 parameters, full schema coverage, and annotations, the description covers pagination, search scope, and return fields (ID, name, details). However, the inaccuracy in default values undermines completeness slightly.

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%, baseline is 3. The description adds context about keywords (nom, email, compétences) but contains inaccuracies: description states pageSize default 20 and max 100, while schema shows default 30 and max 500. The contradiction reduces reliability.

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 'Recherche des drapeaux dans BoondManager par mots-clés avec pagination', specifying a search action on flags with keywords and pagination. It distinguishes from siblings like boond_flags_get by focusing on search.

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 lacks any guidance on when to use this tool vs alternatives like boond_flags_get. It does not mention when not to use it or provide context for choosing between related tools, leaving the agent without decision support.

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