get_all_spring_guides

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

No annotations are provided, so the description carries the full behavioral burden. It says it returns an unfiltered-or-filtered list but discloses nothing about pagination behavior, default page size, result ordering, or whether the list is exhaustive despite 'limit' defaulting to 20.

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?

A single efficient sentence with the verb and resource front-loaded and the optional filter mentioned after. No wasted words, though it is arguably terse to the point of under-specification rather than truly concise.

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 two-parameter read tool with 100% schema coverage and no output schema, the description is minimally adequate. However, with no annotations, it should say more about return shape and pagination behavior to be fully complete.

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 'limit' and 'category' are already documented in the schema, including examples and bounds. The description only alludes to the category filter and adds no syntax or semantics beyond that, so the baseline of 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 states a specific verb and resource ('Récupère la liste de tous les guides Spring') plus an explicit scope ('tous'), making the plural-list nature clear. It does not explicitly distinguish itself from the singular sibling get_spring_guide, but the 'tous' qualifier does most of that work.

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 phrase 'optionnellement filtrés par catégorie' hints at the filtering capability but gives no when-to-use guidance, no prerequisites, and no routing toward alternatives like get_spring_guide or search_spring_docs. An agent must infer usage from the name alone.

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