confluence_update_footer_comment

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

Discloses output trimming and the 'full' parameter override, which is useful. However, with no annotations, it misses details like permission requirements, version conflict handling, or whether the update replaces the entire body.

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 sentences, front-loaded with purpose, no fluff. Every sentence adds essential 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?

No output schema, yet description does not explain what the trimmed vs raw response contains. Absent details on how to obtain commentId/version or handle errors. Could benefit from mentioning comment scope (page vs blog post).

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 100%, so baseline is 3. Description adds value for the 'full' parameter (explaining raw response) but offers no additional meaning for commentId, body, or version beyond their schema descriptions.

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 clearly states 'Update an existing footer comment' with a specific verb and resource. It distinguishes from sibling tools like create and delete by focusing on update.

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?

No explicit guidance on when to use this tool vs alternatives. Does not compare to create or get siblings, nor mention prerequisites or error conditions.

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