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

Annotations already mark the tool read-only and idempotent, and the description adds substantial behavioral detail: the prose is editorial and labelled as such, it has no legal weight, omitting the pathway returns the catalogue, and an unknown id is refused with nothing substituted. This goes well beyond the annotation baseline.

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 front-loaded with the core purpose and each sentence adds distinct information: content of a pathway, editorial/legal caveat, and parameter behavior. It is compact with no filler.

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?

With one optional parameter, rich annotations, and an output schema present, the description covers purpose, usage, content shape, failure behavior, and catalogue access. Nothing critical is missing for an agent to select and invoke the tool correctly.

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%, so the schema already documents the pathway parameter. The description reinforces the omit-for-catalogue behavior and adds the failure mode for unknown ids, which provides extra semantic value beyond the schema.

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 opens with a concrete user need ('Where do I start... in what order?') and defines the resource as curated reading pathways into the corpus, with ordered waypoints, cite anchors, defined terms, and pitfalls. This clearly distinguishes get_orientation from the sibling search and fetch tools.

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 gives clear context for when to use the tool: when a user needs a starting point and reading order on a subject. It also provides an exclusion ('never legal weight') and explains catalogue versus pathway behavior, though it does not explicitly name alternative sibling tools for comparison.

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