Fetch a raw ParentSquare page

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

Annotations already cover read-only and non-destructive behavior. The description adds that it uses the session, can return raw HTML, and serves as a debug escape hatch for inspecting unexpected layouts. No contradictions, though it doesn't mention potential performance or size implications beyond the limit parameter.

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 concise sentences, front-loaded with the 'Escape hatch' framing, which immediately conveys the tool's nature. Every word earns its place without redundancy.

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 readOnly/openWorld annotations, 100% schema coverage, and an output schema present, the description effectively adds the essential usage context. It covers purpose, when to use, and the raw/text distinction, leaving no significant gaps.

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 schema covers all three parameters with detailed descriptions, so the description adds little beyond restating that it fetches any path and can return raw HTML. The schema carries the burden, so a baseline 3 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?

The description clearly states it fetches any ParentSquare path with the session and returns text or raw HTML. It distinguishes itself from the many sibling tools by positioning as an 'escape hatch' for any path, which is distinct from dedicated resource-specific 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?

Explicitly provides when to use: 'when another tool reports that nothing matched the expected layout' or 'to reach a section this server has no dedicated tool for.' This gives clear usage context and implicitly names alternatives (dedicated sibling tools) without listing them.

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