save

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

With no annotations provided, the description carries full burden but only states the action ('save') without disclosing behavioral traits like whether it overwrites existing patterns, requires specific permissions, or handles errors. It mentions 'metadata' but doesn't clarify what that entails or how it affects the save operation.

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 concise with a single sentence, 'Save pattern with metadata', which is front-loaded and efficient. However, it could be more structured by elaborating slightly to improve clarity without losing brevity.

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 no annotations, no output schema, and a mutation tool (save implies write operation), the description is incomplete. It doesn't cover return values, error handling, or behavioral context, making it inadequate for safe and effective use by an AI agent.

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 50% (only 'name' has a description), and the description adds minimal value by implying 'metadata' includes 'tags', but it doesn't explain parameter semantics beyond what's in the schema. With two parameters and partial coverage, this meets the baseline but doesn't compensate for gaps.

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' states the action (save) and resource (pattern) but is vague about what constitutes 'metadata' and doesn't differentiate from sibling tools like 'write' or 'append'. It's better than a tautology but lacks specificity about the pattern's nature or context.

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 like 'write', 'append', or 'generate_pattern'. The description implies saving with metadata, but it doesn't specify prerequisites, exclusions, or typical use cases, leaving the agent to infer usage from context alone.

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