retrieve_page

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

Annotations already convey read-only and non-destructive safety. The description adds behavioral nuance by explaining how project_id changes the resource type (project page vs. workspace page), which is valuable beyond the annotations. It doesn't overexplain, but the conditional behavior is a meaningful disclosure.

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 two sentences, front-loaded with the main action ('Retrieve a page by ID'), and every word adds value. No redundancy or fluff.

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?

For a simple 2-parameter retrieval tool with solid annotations, the description covers the essential decision (project vs. workspace page). It does not explain error behavior or return format, but given the tool's simplicity and the absence of an output schema, this is acceptable. It's nearly complete for its complexity.

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?

While the schema has 0% description coverage, the description itself explains both parameters: page_id is the identifier for the page, and project_id is the selector for project vs. workspace page. This adds semantic meaning beyond the schema's type definitions and defaults, though it could be more explicit about the exact values or constraints.

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's function with a specific verb and resource: 'Retrieve a page by ID.' It distinguishes from sibling retrieval tools by targeting 'page' uniquely. The conditional clause about project_id adds scope precision, making the purpose unambiguous.

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 guidance on when to use this tool for project pages vs. workspace pages: 'If project_id is provided, retrieves a project page; otherwise retrieves a workspace page.' It doesn't explicitly mention alternatives or exclusions, but the conditional context is sufficient for a straightforward retrieval tool.

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