Ops MCP Server

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

With no annotations provided, the description carries full burden. It discloses the read-only nature ('Read'), mentions performance characteristics ('slower'), and describes output behavior ('converted to clean readable text'). However, it doesn't cover important behavioral aspects like error conditions, rate limits, authentication requirements, or pagination behavior.

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 perfectly structured with a clear purpose statement followed by a well-organized parameter explanation. Every sentence earns its place - the first sentence states the core function, and the parameter explanations are essential for proper usage. No wasted words or redundancy.

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?

Given the tool's moderate complexity (4 parameters, read operation) and the presence of an output schema, the description provides good coverage. It explains the core functionality and parameters well, though it could benefit from more behavioral context about errors or limitations. The output schema handles return value documentation, so the description appropriately focuses on usage.

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?

With 0% schema description coverage, the description fully compensates by explaining all 4 parameters with clear semantics: page_id vs title trade-offs, space_key requirement logic, and include_metadata default behavior. The 'Args:' section provides essential context beyond what the bare schema offers.

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 specific action ('Read the full content'), target resource ('a Confluence page'), and output format ('converted to clean readable text'). It distinguishes itself from siblings like get_page_attachments or get_page_comments by focusing on page content specifically.

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 provides implied usage guidance through parameter explanations (e.g., 'Provide this OR title', 'slower, requires space_key'), but doesn't explicitly state when to use this tool versus alternatives like search_confluence or get_child_pages. No clear exclusions or sibling comparisons are provided.

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