Tap

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

Annotations declare readOnlyHint=true and openWorldHint=true, establishing it as a safe external network operation. The description adds that the operation includes 'parsing,' indicating processed output rather than raw bytes, but omits return format, size limits, timeout behavior, or error handling.

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?

Extremely concise single sentence with no redundancy. However, given the behavioral complexity implied by 'download,' 'parse,' and 'inspect,' the brevity may constitute under-specification rather than efficient communication.

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?

Lacks output schema and fails to describe return values, error conditions (404s, timeouts), or what the 'parsed' result actually contains. For a tool performing external I/O and content processing, the description is insufficient to predict outcomes.

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?

With 0% schema description coverage, the description must carry full parameter documentation. It confirms the 'url' parameter is indeed a URL, but provides no format constraints, protocol requirements (http vs file), or encoding details necessary for successful invocation.

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 states the core action ('Download and parse') and resource ('URL'), but fails to specify what 'parse' means (e.g., into DOM, JSON, headers?) or how this differs from sibling tools like forge_save or tap_nav. It functionally identifies the tool but leaves critical scope ambiguity.

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 provided on when to use this tool versus alternatives like tap_nav (navigation) or forge_save (likely persistence). No prerequisites, constraints, or typical use cases are mentioned.

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