Read the full review

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context about the operation being a full-page read beyond a preview, but does not disclose additional behavioral details such as output size, pagination, or error cases.

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?

A single, front-loaded sentence conveys purpose, source, and usage condition with no redundancy. Every word earns its place, and the condition ('when the preview is not enough') is placed at the end without obscuring the main action.

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?

The tool is simple: one required parameter, clear schema coverage, and annotations that establish safety. The description explains when to use it and what it opens, and the output schema exists to define return values. It is complete enough, though it could slightly strengthen guidance on the expected context after a search result.

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 input schema has 100% description coverage: the only parameter 'id' is clearly described as an 'Exact Subject or Observation ID returned by a Pod search result.' The main description reinforces this by linking it to a Pod search result, but adds little beyond what the schema already provides.

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 uses a specific verb ('Open') and names the resource ('complete review or subject page'), sourced from a Pod search result. It clearly distinguishes this from siblings like 'search' and 'inspect_mcp' by focusing on opening the full page rather than searching or previewing.

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 states a clear trigger condition: 'when the preview is not enough.' It implies the tool is used after a Pod search result, but it does not explicitly mention when not to use it or name alternatives, so it falls short of full usage routing.

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