invariance_kb_page_get

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

The annotations already provide readOnlyHint and openWorldHint, but the description adds no behavioral detail beyond what the schema and annotations imply. It does not mention not-found behavior, return shape, or what 'open world' means for this lookup. No contradiction exists, but there is no added transparency.

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 front-loaded sentence with no filler or redundancy. Every word contributes to the meaning.

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 read tool, the description is mostly sufficient for invocation. However, because there is no output schema, the description does not characterize what the returned page object contains or how missing/invalid IDs are handled, leaving mild ambiguity.

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 0%, so the description must compensate. The phrase 'by ID' tells the agent that the sole required parameter is the page identifier, but it does not explain the ID's format, how to obtain it, or any constraints. This is partial, not full, compensation.

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 ('Get'), resource ('knowledge-base page'), and lookup key ('by ID'). It is clearly a read-by-identifier tool and is distinguishable from the list/create/update/delete KB sibling tools, though it does not explicitly name those alternatives.

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?

Usage is implied: call this when you already have a page ID and need that page's content. However, there is no explicit guidance on when to prefer invariance_kb_pages_list instead, nor any stated exclusions or prerequisites.

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