confluence_comment_reopen

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

No annotations provided. Description discloses return format (YAML) and that it mirrors a CLI command, but lacks details on side effects, permissions, or idempotency. Adequate for a simple reopen action.

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 sentences, each earning its place: action, scope, return format, and reference. Front-loaded with verb and resource. No unnecessary words.

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?

Given the simple tool (single param, no output schema), the description is largely complete. It mentions return format, source of ID, and inline-only constraint. Could mention error cases or required permissions for full completeness, but not critically missing.

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 covers 100% of the one parameter. Description adds value by noting comment_id comes from confluence_comment_list and that the tool is for inline comments only, providing context beyond the schema.

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?

Clearly states the verb 'reopen', resource 'resolved inline Confluence comment', and specifies it's for inline comments only using comment_id from confluence_comment_list. Distinguishes from sibling tools like confluence_comment_resolve.

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?

Explicitly says 'Reopen a resolved inline Confluence comment' and 'Inline comments only', giving clear context for when to use. Does not explicitly list alternatives or when not to use, but purpose is sufficiently specific.

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