Get Page

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. The verb 'Fetch' implies a read-only operation, but the description does not explicitly state that it has no side effects or require any permissions. For a simple fetch, this is adequate but not rich; it does not mention return format or error behavior, though the output schema covers some of this.

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 a single, focused sentence that front-loads the primary action and resource. It contains no filler or redundancy, making it efficient for an agent to parse.

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 simplicity, the existence of an output schema, and the complete parameter documentation, the description covers the essential context: what it does, what it takes, and the two page types. It does not explicitly mention error handling or pagination, but these are not critical for a single-fetch operation. The description is sufficient for correct invocation.

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 description coverage is 100%, so both parameters are well documented in the schema. The description's note about workspace vs project page adds context that mirrors the schema's project_id description, but does not introduce new semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb ('Fetch') and resource ('page by UUID'), and clarifies the two possible page types (workspace wiki page or project page). This clearly distinguishes it from siblings like list_pages, update_page, and delete_page, which have different purposes.

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 clear context on when to use the tool: when you have a page UUID and need to retrieve a single page. It implicitly distinguishes from listing tools and project/work item fetchers, though it does not explicitly name alternatives or exclusions. The differentiation between workspace and project pages gives usage context.

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