openstack_list_routers

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

With no annotations, the description carries the full burden of disclosing behavior. It only says 'List routers', which implies a read-only operation, but does not explain any side effects, required authentication, or the meaning of the required device_id parameter. The minimal wording adds no context beyond the tool's name.

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, straightforward sentence with no redundancy or filler. It is appropriately concise and front-loaded with the key information.

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 tool has a required parameter (device_id) that seems inconsistent with a simple 'list routers' operation, and the description does not explain this. There is no output schema, so the description should clarify what the response contains or how the parameter affects results, but it does not. Overall, the description is insufficient for an agent to confidently invoke the tool correctly.

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 schema description covers the single parameter 'device_id' with 'OpenStack device ID', so baseline is 3. However, the description does not clarify why listing routers requires a device_id, leaving a potential semantic gap about how the parameter filters or scopes the list. No additional meaning is added beyond 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 'List' and specifies the resource 'routers in OpenStack (Neutron)', making it clear what the tool does. It distinguishes itself from sibling tools that list other OpenStack resources (networks, subnets, floating IPs).

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?

No guidance is provided on when to use this tool versus other OpenStack list tools. It does not mention any prerequisites, filters, or scenarios where this list is preferred over alternatives like openstack_list_networks or openstack_list_subnets.

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