confluence_get_page

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

With no annotations, the description carries full burden. It discloses caching behavior and return of metadata/file path. No mention of permissions or error states, but sufficient for a simple read-and-cache operation.

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 plus a clear argument list. No unnecessary words. Front-loaded with the main purpose.

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?

Missing output schema but description covers return type (metadata+path). Workflow hint compensates. Could mention behavior for non-existent pages, but overall adequate for a simple tool.

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 has 0% param description coverage. The description adds crucial semantics: 'A numeric page ID or a Confluence URL (including short /wiki/x/ links).' This fully defines the parameter's acceptable input types.

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 'Fetch a Confluence page and cache it locally for editing.' Verb 'fetch' and resource 'Confluence page' are specific. It distinguishes from siblings by mentioning caching and subsequent use of confluence_push_page.

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 implies when to use: to fetch a page for local editing and then publish with push_page. It doesn't explicitly contrast with other read-only tools, but provides a clear workflow context.

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