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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: private routes are unreachable, and a read may yield a second item with a one-time-use ticket plus an instruction to call report_outcome. It also discloses that pattern/starter redemptions can return indexed pitfalls, checks, or a pairing suggestion.

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-loads the core action and return value, then adds the constraint and the side-channel behavior. The third sentence is dense with conditional redemption detail but each clause carries distinct information, so little is wasted.

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 no output schema, the description carries the return-shape burden and does so: Markdown document body plus a possible second item with a ticket and follow-up instruction. Combined with the reachability constraint, an agent has enough to call and interpret it 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 description coverage is 100% for the single parameter, so the schema already documents the accepted path/URL forms. The description restates those formats (root-relative path, https://topologyindex.com URL) with an extra example, but adds no new syntactic or semantic constraint beyond the schema baseline.

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 and resource: "Returns the Markdown document of any public page... exactly as HTTP serves it." It also scopes the resource by excluding private tenant routes, which separates it from authenticated retrieval siblings. It does not explicitly contrast with search or get_pattern, so it falls short of full sibling differentiation.

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 clear context on what is reachable (public pages, root-relative paths or the topologyindex.com domain) and how the result feeds a redemption flow that requires calling report_outcome. It never names search/get_pattern as alternatives or states when to prefer this over them, so the routing guidance is implied rather than explicit.

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