doc_parse_url

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the non-persistence side effect and the return value (filename and rendered markdown), which is helpful. However, it does not mention other behavioral aspects such as potential network calls, error conditions, or whether it requires any prerequisites like the receipt existing, leaving some gaps.

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?

The description is two sentences, front-loaded with the primary purpose, and every phrase adds value. It avoids redundancy and delivers the essential information (template usage, non-persistence, return type) without fluff.

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 two-parameter tool with an output schema, the description covers the key functional points but leaves critical details unspecified. It does not explain what 'key' refers to, does not mention prerequisites (e.g., the receipt must exist), and does not address potential errors or edge cases. While the output schema may cover return details, the lack of parameter definitions is a notable gap.

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%, so the description must compensate. It only hints that 'key' refers to an existing receipt ('using an existing receipt as a template') but does not explicitly define either parameter. 'key' remains ambiguous without further clarification, and 'url' is only inferred from the tool name. This is insufficient given the lack of schema descriptions.

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 the tool parses an arbitrary URL using an existing receipt as a template, and explicitly notes it does not persist the result. This specific verb-resource pair and the non-persistence differentiator set it apart from sibling tools like doc_parse or receipt_add, making its purpose unambiguous.

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?

It provides clear context for when to use the tool: when an existing receipt should serve as the template for selectors/strip_tags/language. It also implicitly advises against using it when persistence is needed by stating 'Does not persist the result as a receipt.' However, it does not explicitly name alternative tools or state when not to use it, so it stops short of a full 5.

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