asset_routes_discover

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

No annotations, so description carries full burden. States passive analysis, no unauthorized access, and lists data sources. Lacks detail on output format but adequately describes behavior.

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?

Single focused paragraph with key information upfront. Slightly dense but no wasted content; could benefit from structured list of sources.

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?

Covers main purpose, data sources, passive nature, and prerequisite. No output schema, but agent can infer likelihood. Lacks constraints on environment or timeout behavior.

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 coverage is 100% with parameter description in schema. Tool description does not add new meaning beyond schema's explanation of parameter purpose.

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?

Specifies verb 'discover' and resource 'front-end routes' with explicit sources (DOM links, hash routes, inline scripts, JS bundles, network logs), differentiating from active probing tools. Purpose is 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?

States prerequisite 'need to browser_open the page first' and constraint 'passive analysis only, no active probing'. Does not explicitly compare to sibling tools but context of options implies when to use.

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