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

Annotations already disclose non-readOnly, non-destructive, non-idempotent behavior, so the bar is lower. The description adds genuine workflow context: a description change must be followed by re-rendering the reference image via assets_generate. It omits permission/auth requirements and what the update does to existing renders, but the downstream-invalidation note is real added 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?

Two tight sentences: the capability first, then the required follow-up action. Every clause earns its place and nothing is padded.

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?

No output schema exists, but the description supplies the critical post-edit workflow (regenerate the reference image) that an agent would otherwise miss. For a mutation tool with full schema coverage and annotations, this is complete enough, though it could note what the operation returns.

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 the schema fully documents all six parameters, including the action enum's per-action requirements. The description only restates name/description edits at a high level and adds no syntax or format detail beyond the schema. Baseline 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?

States specific verbs (add, rename, rewrite) against a specific resource (assets: character/environment/object), which distinguishes it clearly from assets_read and assets_generate. The reference to 'Analyze Script missed' gives the concrete scenario the tool exists for. An agent can tell it apart from its siblings 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 a clear when-to-use trigger (when Analyze Script missed an asset) and names the follow-up alternative (assets_generate) for re-rendering reference images. It does not explicitly contrast create vs update behavior in prose, but the schema enum covers that split. Clear context with no strong exclusions stated.

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