vrx_request

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

No annotations are provided, so the description carries full burden. It discloses RSQL query syntax, pagination limits (size <=500, from <=10000, seek paging beyond 10000), and read-only mode restrictions (only GET permitted). This provides comprehensive behavioral context.

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 paragraph that efficiently covers purpose, usage, and behavioral details. It is front-loaded with the main purpose. Minor structure improvements (e.g., bullet points) could enhance readability, but it is concise and informative.

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?

Given the tool's generic nature (no output schema), the description adequately covers input parameters, constraints (read-only mode, pagination), and RSQL syntax. It does not describe return values, which vary by request, but the description is sufficient for a generic request tool.

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 description coverage is 100%, so baseline is 3. The description adds extra meaning: it explains path is relative, specifies RSQL syntax for query parameters, and mentions pagination details. It goes beyond the schema's basic descriptions.

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 issues arbitrary requests to the Vicarius vRx External Data API for endpoints without a dedicated tool. It identifies the specific resource and action, and distinguishes from sibling tools by explicitly mentioning 'for endpoints without a dedicated tool'.

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?

The description indicates when to use this tool (for endpoints without a dedicated tool) and provides context such as read-only mode restrictions. However, it does not explicitly state when not to use it or list alternative tools.

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