confluence_get_page_properties

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

With no annotations, the description only discloses pagination behavior. It does not mention error states (e.g., page not found), rate limits, or what happens when properties are empty. Minimal transparency 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?

Extremely concise: two sentences, front-loaded with purpose, no wasted words. 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?

No output schema, so description should describe return value structure. It does not specify format of content properties or if there are any nested fields. Also lacks differentiation from sibling property tools. Incomplete for a tool with no output schema.

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. The description adds context for the cursor parameter ('use the returned cursor to fetch more'), which is helpful but does not elaborate on limit or pageId beyond what the schema provides. Slightly above baseline but not significantly.

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 retrieves content properties for a page, which aligns with the name. However, it does not differentiate from the sibling tool 'confluence_get_page_property' (singular), which likely retrieves a single property, so the distinction is implicit.

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 explicit guidance on when to use this tool over alternatives. The description mentions pagination but does not compare to other property-related tools or specify prerequisites beyond the required pageId.

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