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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it never says whether omitted fields are preserved or cleared, whether values are replaced wholesale, or what authorization is required — a material gap for a destructive update.

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 that names the action and the affected fields with zero filler. Nothing repeated from the schema or annotations.

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 destructive mutation with no output schema and 20% parameter coverage, the description omits permission requirements, overwrite/merge behavior, and any indication of what the call returns on success. An agent cannot call this with confidence.

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 coverage is only 20% (just forgeId is documented). The description enumerates the four optional fields, but this merely echoes the schema property names and supplies no format, constraint, or merge/replace semantics for name, tags, license, or description.

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 and resource ('Change a forge's name, description, tags or license') and scopes it to listing fields, which separates it from siblings like create_forge, publish_forge, and make_forge_private. It stops short of explicitly naming an alternative, so it is clear but not fully differentiated.

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?

Only implies usage via 'the fields shown on its listing.' There is no statement of when to use this versus make_forge_private, publish_forge, or create_forge, and no prerequisites (ownership/permission) are given.

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