get_pattern

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

No annotations are provided, so the description carries the full burden. It mentions 'Devuelve' (returns), implying a read operation, but it does not explicitly state that it is safe, side-effect-free, or what happens if the pattern is not found. Beyond the primary action, no additional behavioral context is disclosed.

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, concise sentence that is easy to read and front-loaded with the main action. However, its brevity sacrifices important details, making it efficient but not fully informative.

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 tool with one parameter and no output schema, the description offers minimal context. It does not clarify what constitutes an 'agentic pattern' or how the implementation guide is structured, and it lacks any mention of related tools or expected return behavior, leaving the agent with significant gaps.

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 only parameter 'name' has no schema description (0% coverage), and the tool description does not explain that 'name' refers to the pattern's name. With no parameter information in either the schema or description, the agent is left to infer the parameter's meaning from the tool name 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 that the tool retrieves a specific agentic pattern along with implementation guidance, using a verb ('Devuelve') and a resource ('patrón agéntico'). While it doesn't explicitly differentiate from list_patterns, the word 'specific' implies single-item retrieval, which distinguishes it from listing 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?

There is no guidance on when to use this tool versus alternatives such as list_patterns or add_custom_pattern. The description only describes the function without any contextual cues, prerequisites, or exclusions.

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