guide.page

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

No annotations are present, so the description carries the burden. It lists returned content (text, weave, lattice vertex, PSI element, public URL), suggesting read-only behavior, but does not explicitly confirm side effects or permissions.

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?

Single compact sentence conveys the tool's purpose, key parameter guidance, and return contents without unnecessary words.

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 page-retrieval tool, the description is adequately complete: it names the resource, parameters, and output fields. It omits error scenarios, but these are not critical for basic usage.

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 description clarifies that slug is the identity and site is optional, which partially compensates for the sparse schema. It does not explain the format or possible values for slug or site.

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?

Description clearly identifies the tool as retrieving a single page by slug and distinguishes it from search/neighbor tools by emphasizing the slug as the identity. Lacks an explicit verb like 'get' or 'fetch', but the intent is unmistakable.

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?

Gives useful guidance that the slug is the identity and site is optional, but does not explicitly state when to prefer this tool over sibling tools like guide_search or guide_neighbours.

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