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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds no behavioral context beyond those hints. It does not mention overwrite semantics, that omitted fields are preserved, or any side effects. There is no contradiction with annotations, but the description relies entirely on them.

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?

The description is a single sentence with no filler. It front-loads the verb and resource and enumerates the relevant fields immediately. Every word contributes meaning.

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 simple update tool with an output schema and 100% parameter coverage, the description is mostly adequate. However, it fails to clarify that at least one of name, slug, or description should be provided, despite these fields not being marked required in the schema. An agent could call the tool with only blogId and collectionId and produce a no-op or unexpected result.

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 baseline is 3. The description only echoes the field names from the schema and adds no additional meaning about formats, relationships, or constraints. The useful 'Use list_blogs' guidance is already in the schema, not the 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?

The description names a specific verb ('Update'), a clear resource ('existing collection'), and the exact mutable attributes ('name, slug, or description'). This is unambiguous and differentiates the tool from sibling tools like create_collection, delete_collection, or update_blog.

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 description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no explicit when-not-to-use conditions. It merely states what the operation does. Unlike the calibration example for get_calls, no sibling tool is mentioned for routing.

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