perch_pull

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

With no annotations, the description carries the full burden and does well: it discloses ~1.2s latency, no auth/collab key requirement, that it writes files locally, and independence from perch_start. It omits failure modes and overwrite/refresh behavior, which keeps it from a 5.

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 key differentiator ('BROWSER-FREE code access') and packs timing, constraints, and workflow into three dense sentences. The em-dash clauses are information-rich rather than filler, though slightly crowded.

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 2-param tool with no output schema or annotations, it covers what is fetched, where it lands, timing, and prerequisites. Return-value details are unnecessary since the payload is written to files, but overwrite/refresh semantics remain unstated.

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%, so both params (dir, name) and their defaults are already documented in the schema. The description adds no syntax or default behavior beyond what the schema provides, so baseline 3 applies.

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 (Fetch) plus the exact resources (modelText/main.pjs, outputTemplate/index.html) and the side effect (write to local files). An agent can distinguish it from siblings like perch_fetch_generator or perch_start without opening any schema.

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: browser-free, no Cloudflare, no collab key, and explicitly 'Works without perch_start', plus the downstream workflow ('Grep/read those files directly'). It stops short of naming an explicit alternative or a when-not-to-use condition versus perch_fetch_generator.

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