confluence_get_page_properties

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

Annotations are absent, so the description carries the full burden. It discloses that the operation is a read ('Get') and describes the return type as key-value pairs, but lacks details on authentication, rate limits, error behavior (e.g., if page_id is invalid), or idempotency. No contradiction with annotations since none exist.

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 concise with a clear structure: one-line summary, a brief explanation of content properties, then parameter details. No redundant sentences. Could be slightly more structured with explicit sections.

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 tool with 2 parameters and no output schema, the description covers the basics but lacks completeness: no response format, error handling, rate limits, or usage context. It is adequate but not comprehensive.

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 description adds meaning beyond the schema: page_id accepts numeric ID or Confluence URL (including short links), limit has default 25 and max 100. This compensates for the schema's 0% parameter description coverage. However, it does not explain the format of key-value pairs returned.

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 'Get content properties on a Confluence page' and explains that properties are key-value metadata. The verb 'get' and resource 'page properties' are specific. However, it does not explicitly distinguish from sibling tools like 'confluence_get_page' or 'confluence_get_labels', but the purpose is unambiguous.

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 tool vs alternatives (e.g., confluence_get_page for the page itself). It does not mention prerequisites, context, or when not to use it. The description only explains parameters, not usage scenarios.

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