confluence_get_page_footer_comments

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

Without annotations, description reveals pagination behavior, default output trimming, and option for raw response. Missing details on error cases or permissions, but sufficient for a read 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 with no waste. Key information front-loaded. Every sentence adds value.

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?

Covers main aspects (pagination, trimming) but lacks details on response structure, error handling, or permissions. Adequate for a simple read 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 coverage is 100%, so baseline is 3. Description adds context about pagination cursor and full parameter's effect on trimming, but does not elaborate on other parameters beyond 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?

Description clearly states 'Get footer comments on a specific page' with specific verb and resource. It distinguishes from sibling tools like confluence_get_page_inline_comments (different comment type) and confluence_get_blog_post_footer_comments (different content type).

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?

Provides guidance on pagination (use returned cursor) and response trimming (full=true for raw). Does not explicitly state when to use this vs alternatives, but purpose is specific enough to infer.

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