Pontis

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

Annotations already declare readOnly, idempotent, and closed-world behavior. The description adds valuable context beyond that: it specifies the return format (markdown), the comprehensive scope (every page on the site), and the presence of authoritative 'facts that must not be inferred'—a behavioral caveat not captured by annotations.

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?

A single, front-loaded sentence that opens with the core action and format. The enumeration of contents is lengthy but informative and earns its place by detailing what the guide includes.

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 zero-parameter, read-only tool with no output schema, the description adequately explains what is returned (a markdown site guide with detailed sections). The only gap is guidance on when to use this tool instead of read_page.

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 tool has zero parameters, so parameter semantics are not applicable. Baseline score of 4 is appropriate.

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 ('Returns') and resource ('Pontis site guide (llms.txt) as markdown') and enumerates the content scope. This clearly distinguishes it from a generic page reader, though it does not explicitly name the sibling tool read_page.

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 no explicit when-to-use guidance, prerequisites, or alternatives. The agent must infer that this is the entry point for site-level information versus read_page for individual pages.

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

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, closed world), so the description's job is to add return-shape context, which it does: output is markdown with navigation and footer removed. It does not address behavior on a nonexistent path (404/error handling), which is the main remaining gap for a fetch tool.

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?

Two tight sentences: the first front-loads what is returned and in what format, the second tells the agent exactly what to supply. No filler or restated field definitions.

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 required parameter, no output schema, and full annotation coverage, the description supplies the missing return-format detail itself. Only the absence of error/not-found behavior keeps it from being fully complete.

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 baseline would be 3; the description earns above that by giving concrete example values ('/'), '/about', '/about', '/knowledge', '/events/intercept') that convey the real URL structure and path format beyond the schema's generic 'path starting with /' hint.

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 one page of pontis.company as markdown') plus the transformation applied (navigation and footer stripped). It does not, however, distinguish itself from the sibling get_overview, which is never mentioned.

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 by the instruction to 'Pass its path' with example routes, so an agent can infer this is the fetch-by-URL-path tool. There is no explicit when-to-use versus get_overview guidance or any stated condition/precondition for choosing this tool over the sibling.

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