save

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

With no annotations, the description carries full burden but provides minimal behavioral info. It implies a mutation (save) but doesn't disclose side effects (overwriting, required state, validation) or return value.

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?

Extremely short (4 words), but this brevity sacrifices clarity. Useful details about scope, persistence, and behavior are omitted, making it under-specified rather than 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?

Given the complexity (many sibling tools, no output schema), the description fails to provide adequate context. It doesn't explain what 'save' means in this environment or how the pattern is retrieved later.

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 describes 'name' (Pattern name) but 'tags' lacks description. The description's 'with metadata' hints at tags' role but adds little value. With 50% schema coverage, the tool should compensate more.

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 'Save pattern with metadata' identifies the action (save) and resource (pattern), but it's vague on what saving entails (persistence location, session context). It distinguishes from 'load' but not from 'write', a sibling with potentially overlapping functionality.

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 explicit guidance on when to use this tool versus siblings like 'write' or 'export_midi'. The description does not state prerequisites (e.g., active session) or expected context.

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