confluence_extract_text

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

No annotations provided. The description explains the read-only behavior (fetching ADF, converting to plaintext) but does not explicitly state non-destructive nature or disclose potential limitations like page size, rate limits, or authentication requirements.

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 brief and front-loaded: first sentence states core purpose, followed by a clear param explanation. No redundant 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 tool has one parameter and no output schema. The description explains the parameter well and mentions the output format (plaintext with basic formatting), but does not specify return structure, error handling, or edge cases. Adequate for low complexity but could be more complete.

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?

The only parameter, page_id, is well-documented in the description: it accepts numeric IDs, full URLs, and short /wiki/x/ links. This adds significant value over the schema which only specifies type string.

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 the tool extracts plain text content from a Confluence page, with specific verb and resource. It distinguishes from sibling tools that modify or manage pages.

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 guidance on when to use this vs alternatives, and no exclusions or context provided. The user is left to infer usage from the purpose alone.

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