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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description adds nothing on top: it doesn't say whether repeated saves create duplicates (relevant given idempotentHint=false), whether content is validated or truncated, or what is returned. With annotations carrying the whole burden, the description contributes almost no extra context.

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?

A single front-loaded sentence with no filler or repetition. It is appropriately sized, though it spends its only sentence on purpose and leaves no room for routing or behavioral notes.

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?

For a four-parameter write tool with no output schema, an agent needs to know what a successful save returns (an id? the stored record?), and whether business_profile_id is optional or required in practice. Neither is addressed, and the duplicate-save behavior implied by idempotentHint=false is left unexplained.

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%, with every field documented including maxLength bounds and the markdown allowance for content. The description adds no syntax or semantic detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb plus resource and destination: 'Saves a piece of marketing copy or strategy to the user's Marketing Vault library.' That is enough to tell it apart from generation siblings like write_ad_copy and from list_saved_outputs, though it never names those alternatives explicitly.

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?

There is no explicit when-to-use guidance, no preconditions, and no mention of when to prefer save_reference_note, add_proof, or add_standing_rule instead. The intended workflow (save after generating copy) must be inferred entirely from the word 'library' and the sibling names.

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