raw_request

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

With no annotations, the description carries the full burden. It usefully discloses that the 'read' default is often wrong and that valid shapes are model-specific, which is real behavioral value. However, it never warns that 'write' operations mutate router configuration, says nothing about permissions, reversibility, or error/response behavior for a tool that can hit any endpoint.

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?

Three compact lines: purpose first, then the operation gotcha, then the discovery pointer. Every sentence earns its place, though the fragmentary example-first formatting makes it slightly disjointed.

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 generic, unannotated, write-capable escape hatch with no output schema, the description supplies the essential discovery route via list_endpoints. It still leaves gaps an agent needs: how params maps to the request, what a response looks like, and what the consequences of a 'write' operation are on the router.

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 0%, so the description must compensate. It explains form_path by example and clarifies operation's default and that non-'read' values are commonly needed, but the params object — the payload for the request — is not described at all, and the shape of form_path (query-string form) is only shown, not specified.

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?

States a specific verb and resource ('Call any router endpoint') and immediately grounds it with a concrete example (form_path='status?form=client_status', operation='load'). The 'escape hatch' framing distinguishes it from the many specific get_/set_ siblings, though it never names those siblings directly.

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?

Gives an explicit discovery workflow ('Use list_endpoints() to discover valid form paths, operations, and shapes') and a concrete trigger condition (many forms need 'load'/'write' rather than the default 'read'). 'Escape hatch' implies preference for dedicated tools, but no explicit when-not-to-use statement is made.

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