load

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

With no annotations, the description must reveal behavioral traits. It states 'Load saved pattern' but does not disclose whether the operation is destructive (overwrites current pattern), requires permissions, or has side effects like modifying session state.

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 (2 words), which is efficient but lacks necessary details. While it avoids verbosity, the brevity comes at the cost of completeness.

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 tool's simplicity (1 param, no output schema), the description is still too sparse. It fails to explain the operation's effect on the current pattern or session, leaving the agent uncertain about behavior.

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 schema has 100% coverage with one parameter 'name' described as 'Pattern name'. The description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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' uses a clear verb and resource, indicating the tool loads a previously saved pattern. However, it does not elaborate on what 'load' entails (e.g., replacing current pattern, merging, or selecting), and lacks differentiation from siblings like 'get_pattern' which retrieves pattern data.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_pattern', 'save', or 'list'. The agent receives no context about prerequisites (e.g., pattern must exist) or whether loading clears the current session.

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