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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description adds genuine behavioral context instead: metadata fields are auto-generated, so the agent can call immediately without a clarification round-trip. It stops short of disclosing what happens on a duplicate slug or whether re-saving overwrites an existing skill.

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?

Front-loaded with the invocation trigger, then the required-field fact, then the 'don't stall on metadata' instruction, then two routing sentences. Roughly seventy words with no filler and every sentence carrying a distinct decision the agent has to make.

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?

There is no output schema, so the description should ideally say what comes back on success or what a same-name save does; it doesn't. Everything an agent needs to decide whether and how to invoke the tool, including the brand-scoping fallback covered by the schema, is otherwise present.

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 100%, so every field including auto-derivation of name/slug is already documented in the schema. The description's 'Only `procedure` is required' and the auto-generation note largely restate the required array and the schema's own 'it's derived automatically' text, adding emphasis rather than new meaning.

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?

States a specific verb (save) plus the resource (skill/workflow/repeatable method) and defines it in contrast to near-misses: a procedure to follow, 'not fixed text to run.' That negative definition lets an agent separate it from save_prompt and remember_brand_fact without opening any schema.

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?

Gives explicit trigger conditions ('when the user asks to save a skill, a workflow, or a repeatable method'), explicit exclusions routed to named alternatives ('use save_prompt, not this' / 'use remember_brand_fact'), and an explicit anti-pattern ('Do not pause to ask the user for a name, slug, or description first'). This is the full when/when-not/alternative triad.

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