find_route

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

Discloses the underlying console command, requirements for PHP environment, return format (Markdown table with specific columns), and behavior for single matches. No annotations are provided, so the description carries the full burden.

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?

Well-structured with purpose first, then method, parameters, output, and requirements. No redundancy, but could be slightly more 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?

Covers prerequisites (PHP access), parameters, output format, and behavior for single vs multiple matches. Completeness is appropriate for a tool that runs an external command.

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 adds substantial meaning: explains url_pattern as substring or regex with examples, and method as optional filter with examples. Slightly more detail on regex format could improve, but overall effective.

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 it finds Symfony routes matching a URL pattern or route name, specifying the command used. This distinguishes it from sibling tools like search_code and find_symbol.

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?

Provides explicit examples for url_pattern and method parameter, indicating when to use. However, it does not explicitly state when not to use or compare to alternatives.

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