get_page

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

With no annotations, the description carries the full behavioral burden, and it does disclose the return format (markdown) and the failure mode (error if the page ID is not found). It does not mention permission requirements, size limits, or what to do if the ID is unknown (e.g., fall back to search), so it is strong but not exhaustive.

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?

Front-loaded with the core purpose in the first sentence, followed by workflow context and a bullet list. The bullets restate some of the prose above them, which is mildly redundant but still scannable and short overall.

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 single-parameter lookup tool with no output schema, the description covers purpose, how to source the ID, the trigger conditions, the return format, and the error case. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the schema already gives example IDs, so baseline is 3. The description adds meaning beyond the schema by stressing the ID must be 'exact' and by explaining the primary way to obtain it — from [PageID] citations in other tools' responses.

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?

States a specific verb (retrieve) and resource (knowledge base page) with its key constraint: lookup by exact ID. It is clearly distinguishable from sibling search_knowledge because it explicitly says it reads a specific page 'without searching'.

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?

Provides an explicit when-to-use list with three concrete triggers, including the citation-follow-up workflow ([PageID] seen in another tool's output). This tells the agent both when to reach for this tool and what upstream signal selects it.

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