get_all_urls

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states which tag types are scanned but does not mention whether URLs are returned as absolute or relative, how the 'absolute' parameter affects output, whether results are deduplicated, or that the operation is read-only. These behaviors are left to inference.

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 a single focused sentence with no filler. It front-loads the main action and adds useful specificity by listing the relevant element types, making it appropriately concise.

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 simple tool with one optional boolean parameter and an output schema, the description covers the core extraction scope, but it omits the behavior of the 'absolute' parameter and gives no usage context relative to sibling tools. These gaps prevent the definition from being fully self-sufficient.

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 does not mention the 'absolute' parameter at all. The agent can only guess that 'absolute' controls whether returned URLs are resolved to absolute form; the description adds no meaning beyond the parameter name and default value already present in the schema.

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 uses a specific verb ('Get') and a clear resource ('all linked URLs'), and it enumerates the exact element types involved (a, link, img, script, meta). This clearly distinguishes it from sibling getters like get_current_url or get_html_source.

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?

There is no explicit guidance about when to use this tool versus alternatives such as get_current_url, get_text, or get_html_source. The intended context is only weakly implied by 'all linked URLs' and the element list, so the agent must infer when this tool is the right choice.

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