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

Beyond annotations, it discloses that updates persist to the database, cache is invalidated, the operation is free, and authentication/ownership is required. These are useful behavioral details. It stops short of clarifying partial-update semantics (e.g., whether omitted fields are preserved), which is a notable gap for a destructive edit tool.

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?

Three compact sentences front-load the action and field scope, then add persistence/cache behavior, cost, and auth requirements. Every sentence contributes distinct, useful information.

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?

The description covers the essentials for a destructive edit operation: what can be changed, that changes are persisted, cache invalidation, cost, and auth/ownership. It would be stronger if it stated whether this is a partial update or full replacement of the provided fields.

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 already documents the parameters and enums. The description adds only a high-level list of editable fields and does not explain partial update behavior or element replacement semantics beyond what the schema provides.

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 and resource: 'Edit existing infographic content.' It also enumerates the editable fields (title, description, layout, visual style, elements), making it clear this differs from create_infographic and from non-infographic edit tools.

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?

The phrase 'Edit existing infographic content' implies use when modifying an existing infographic, and it states a key prerequisite: 'Requires authentication and ownership.' It does not explicitly name alternatives or exclusions, but the operation is sufficiently self-routing for an edit tool.

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