get-page-by-id

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states 'Find a page by its ID' and does not mention default version behavior, response shape, error handling, or authentication requirements. The schema provides some parameter context, but the description itself adds zero transparency beyond the tool's name.

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, perfectly concise sentence with no redundant words. It is well-structured and front-loaded, but is so terse that it omits potentially useful context, though this does not detract from its conciseness.

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?

Despite having 3 parameters and no output schema or annotations, the description remains minimal. It fails to explain version defaults, includes behavior, or what a successful response contains. The schema covers parameter semantics, but the overall tool context is incomplete, especially for an agent deciding how to handle the response.

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% with clear descriptions for pageID, version, and includes. The description adds no additional parameter meaning, but per rubric baseline for high coverage is 3, so the schema already carries the semantic weight.

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 'Find a page by its ID' uses a specific verb ('find') and resource ('page') with an explicit identifier, clearly stating the tool's function. It distinguishes from sibling get-by-id tools by specifying 'page' rather than group, site, user, file, or block, and from get-page-version-by-page-id-and-version-id by targeting pages rather than versions.

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 no guidance on when to use this tool versus alternatives like get-pages, get-page-version-by-page-id-and-version-id, or get_page_content. It does not mention prerequisites, common use cases, or exclusions, leaving the agent to infer usage from the name alone.

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