list_requests

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

Thoroughly explains all parameters and their effects (filtering, sorting, pagination, field selection, display values). However, lacks explicit mention of read-only nature or idempotency.

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?

One paragraph that front-loads purpose, then efficiently describes each parameter in a sentence. No superfluous text.

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 all 7 parameters, includes examples and default behaviors, and is sufficient given the presence of an output schema.

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 tool description fully compensates by providing clear explanations and an example for the query parameter, plus descriptions for all other parameters.

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?

Clearly states it lists/searchs service request records from the sc_request table, distinguishing it from sibling tools like list_incidents and list_requested_items.

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?

Implies usage for listing requests, but does not explicitly compare to alternatives like list_table_records for other tables, nor provides when-not-to-use guidance.

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