Fetch GitHub Pages content

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

With no annotations provided, the description carries full burden and does well by disclosing the use of a persistent local browser profile and explicitly stating it never reads the source repository. This gives useful behavioral context beyond the basic fetch action, though it omits details like return format or auth requirements.

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, front-loaded sentences. The first delivers the core action, and the second adds a critical behavioral boundary. No unnecessary words or repeated schema information.

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?

The core behavior and a key limitation are clear, but the description lacks parameter explanations, usage guidance, and return value expectations. Given no annotations and no output schema, the description is not fully complete for invoking the tool correctly in various contexts, though it covers the essentials.

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 0%, and the description provides no information about the 'url' or 'sourceId' parameters. The agent must guess their meanings from the schema alone, which only provides names and types but no semantics.

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 one allowlisted GitHub Pages URL using a persistent local browser profile. It also explicitly distinguishes itself by noting it never reads the source repository, which separates it from sibling tools that may access repositories.

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?

No explicit guidance is provided on when to use this tool versus alternatives like fetch_indexed_section or search_pages_index. The description implies a specific use case (fetching a direct URL) but lacks context for choosing it over siblings.

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