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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Retrieve' implies a read-only operation, the description fails to specify error behavior (e.g., what happens if the ID doesn't exist), authentication requirements, rate limits, or the structure of the returned page data.

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 extremely concise at four words with no filler. However, given the lack of annotations and output schema, this brevity leaves critical gaps in documentation, suggesting it may be undersized for proper tool invocation despite not being verbose.

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 lacks both annotations and an output schema, yet the description doesn't compensate by describing the return format, page structure, or error states. For a retrieval tool, omitting what gets returned represents a significant completeness gap despite the simple single-parameter input.

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 schema has 100% description coverage ('ID of the page to retrieve'), so the baseline is 3. The description implies the ID parameter with 'by ID' but adds no additional semantic context—such as ID format or where to obtain it—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 ('Retrieve') and resource ('page') and identifies the lookup method ('by ID'), which distinguishes it from search-based siblings like 'search'. However, it doesn't clarify the difference between this and 'get_database' beyond the resource name itself.

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 'search' (which finds pages by query) or 'get_database'. It omits prerequisites such as needing a valid page ID from prior calls.

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