collect_code

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

No annotations are provided, so the description carries the full burden. 'Fetch and cache' implies reading and storing, but it does not disclose the caching behavior (scope, lifetime, overwrite), side effects, or permissions needed. Minimal behavioral information beyond the basic function.

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 sentences, each earning its place. The first sentence states the main action, the second adds the conditional filtering. No redundant words or filler.

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 tool has 3 optional parameters and no output schema. The description does not explain the return value (does it return the source? cache only?), how 'maxScripts' works, or the lifecycle of the cache. For a tool that collects and caches, more behavioral detail is needed to ensure correct invocation.

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 has 3 parameters with no descriptions (0% coverage). The description explains 'urls/urlSubstring' as optional filters, adding meaning beyond the schema. However, 'maxScripts' is not mentioned at all, leaving its purpose unclear. Partial coverage, missing one parameter.

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 'Fetch and cache the source of every script URL on the active page' with a specific verb and resource. It distinguishes from siblings like 'list_scripts' or 'get_script_source' by focusing on bulk collection and caching. However, it does not explicitly differentiate from siblings like 'search_in_scripts' or 'summarize_code', so it falls short of a 5.

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 guidance on when to use this tool versus alternatives like 'get_script_source' (single script) or 'list_scripts' (metadata only). The description mentions conditional filtering but does not explain when not to use it or provide context for choosing among many sibling tools.

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