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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description does not need to cover safety. It adds substantial behavioral context by listing the comprehensive return payload (semantic layer, ontology, example, props/types), which goes beyond the annotation and explains what the agent will receive. No contradiction.

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 compact and front-loaded: one sentence enumerates the detailed content, followed by a direct usage directive. Every word serves a purpose, with no redundant filler, making it highly efficient.

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?

With no output schema, the description must convey what is returned, and it does so thoroughly by listing all content categories. It also explains the name format and usage context. Minor gaps exist regarding exact formatting of props/types or error behavior, but for a single-parameter read tool, this is sufficient for an agent to select and invoke correctly.

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 the schema already fully documents the 'name' parameter. The description repeats the accepted alias ('bpm.metric' or 'metric') without adding new semantic meaning beyond the schema, keeping the score at baseline.

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 returns the complete detail of a component, enumerating the specific content (description, props/types, usage example, associated components, semantic layer). This distinguishes it from siblings list-components and search-components, which are for discovery, making the purpose unambiguous and specific.

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 instructs to use after list/search and before generating code, positioning this tool as the one for obtaining the exact signature and semantic meaning. This gives clear workflow context and implies it is not for initial discovery, effectively differentiating from sibling tools.

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

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

Annotations already declare readOnlyHint=true, so the description goes beyond by disclosing pagination via 'nextCursor', the return format (name + one-line description), and the list of available categories. This adds meaningful behavioral context that is not present in the annotations.

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 compact: a purpose statement, a usage directive, a pagination note, and a category list. Each sentence serves a distinct purpose, and the most important information is front-loaded.

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?

Despite having no output schema, the description specifies what is returned (name + one-line description) and how pagination works. Combined with the rich annotations and clear usage context, it is fully complete for a list tool of this complexity.

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%, so the baseline is 3. The description adds extra value by listing the valid categories (e.g., Graphiques, Feedback), which the schema does not provide as an enum, and reinforces how to reuse 'nextCursor' for pagination.

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 lists components of the Blueprint Modular design system with name and one-line description. It explicitly frames the use case as browsing the catalog or discovering what exists in a category, which distinguishes it from the sibling search_components, get_component, and suggest_composition tools.

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?

It provides explicit usage context ('À UTILISER pour parcourir le catalogue ou découvrir ce qui existe dans une catégorie donnée'), making the primary use case clear. However, it does not explicitly state when not to use it or mention alternative tools by name, so it falls short of the full 5.

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

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

Annotations already mark it as read-only, and the description adds valuable behavioral details such as matching fields (name, description, category, tags), relevance sorting, and cursor-based pagination. No contradiction with annotations.

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?

Three short sentences, each conveying essential information: purpose, usage context, and pagination. No redundant wording; information density is high.

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 two well-documented parameters and good annotations, the description covers what it does, when to use it, and pagination. It doesn't describe the result item structure, but in the absence of an output schema and given sibling tools, this is an acceptable gap.

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%, so the baseline is 3. The description goes beyond the schema by explaining the cursor's role in pagination ('Résultat paginé par curseur') and clarifying that query accepts natural language terms, adding practical meaning.

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 a specific action: 'Recherche les composants pertinents' with a defined search mechanism over name, description, category, and tags, sorted by relevance. It strongly distinguishes itself from sibling tools like list_components (likely a full listing) and get_component (likely by ID) by focusing on free-text 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?

Provides explicit usage direction: 'À UTILISER quand on cherche un composant par fonction ou mot-clé' with concrete examples. It doesn't explicitly mention when NOT to use it or name alternatives, but the context is clear and practical.

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

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

Annotations already indicate readOnlyHint=true, and the description adds useful behavioral context: it mentions the response is bounded ('Réponse bornée') and that each suggestion includes its meaning and semantic associations (pairWith). This goes beyond the annotation without contradicting it.

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 two concise sentences, front-loaded with the primary purpose. Every phrase adds value, no redundancy.

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?

With two parameters and no output schema, the description provides essential context: the tool's semantic reasoning, output structure (meaning, pairWith), and bounded response. It could mention the default/max limit explicitly, but the schema covers that, making it sufficiently 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 coverage is 100%, providing baseline 3. The description adds value by giving a concrete example of the 'need' parameter ('un dashboard avec des métriques et un graphique'), clarifying expected input beyond the schema's generic description.

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 suggests a list of Blueprint Modular components based on a natural language need, using the semantic layer. It distinguishes itself from siblings (list_components, search_components, get_component) by specifying its semantic reasoning and the screen-intention use case.

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 explicitly says to use the tool when starting from a screen intention (e.g., 'un dashboard avec des métriques et un graphique') to obtain relevant components. It provides clear context but does not explicitly name alternatives or state when not to use this tool.

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