get_all_urls

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

No annotations are provided, so the description carries the burden of declaring side effects. 'Get' implies a read-only inspection and the tag list clarifies exactly which page URLs are gathered. It does not discuss normalization, deduplication, or the effect of the absolute parameter, but no destructive behavior or contradiction is indicated.

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 one short, front-loaded sentence with no filler and a precise list of relevant tags. It would benefit from a clause about the absolute parameter, but that omission is a completeness issue, not a conciseness issue.

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 function is simple, has an output schema, and no required parameters, so a terse description is appropriate. Still, the unmentioned absolute parameter and the lack of any routing guidance leave gaps for an agent deciding how to call it or distinguish it from sibling tools.

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?

The only parameter, absolute, has 0% schema description coverage and is never mentioned in the description, so the agent cannot learn from the description what true/false does to the returned URLs. The parameter name gives a hint, but the description adds no parameter-level meaning.

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 names a specific action and object: 'Get all linked URLs' and narrows scope with the explicit tag list '(a, link, img, script, meta)'. It is distinguishable from single-URL tools like get_current_url, though it does not explicitly contrast with sibling scraping tools, so it is not 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?

There is no statement of when to choose this over get_html_source, find_all_info, or get_current_url, nor any exclusion such as 'for same-origin URLs only'. Usage context is only implied by the tool name and description.

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