load

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Load saved pattern' implies a read operation, but it doesn't specify whether this requires authentication, what happens if the pattern doesn't exist, if there are rate limits, or what the output looks like (e.g., does it return the pattern data or just a confirmation?). For a tool with no annotation coverage, this is insufficient behavioral detail.

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 extremely concise with just three words: 'Load saved pattern'. It's front-loaded and wastes no space, making it easy to parse quickly. Every word contributes directly to the core function, earning its place without unnecessary elaboration.

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 the complexity of a 'load' operation in a pattern-processing context with many sibling tools, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'loading' entails (e.g., does it retrieve pattern data for editing, or activate it for playback?), nor does it address potential errors or the return format. This leaves significant gaps for an agent to operate effectively.

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 input schema has 100% description coverage, with the single parameter 'name' documented as 'Pattern name'. The description doesn't add any parameter-specific information beyond this, but with high schema coverage and only one parameter, the baseline is strong. No additional semantic context is needed, so a score of 4 reflects adequate parameter understanding from 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 'Load saved pattern' is a tautology that essentially restates the tool name 'load' with minimal context. While it indicates the action (load) and resource type (saved pattern), it doesn't specify what constitutes a 'pattern' in this domain or distinguish this tool from similar siblings like 'get_pattern' or 'generate_pattern'. The purpose is vague and lacks the specificity needed for clear differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., that a pattern must be saved first), exclusions, or comparisons to sibling tools like 'get_pattern' or 'save'. Without this context, an agent might struggle to choose between this and other pattern-related tools in the list.

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