list_service_orders

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

With no annotations, the description should disclose behavior. It mentions filters but omits default pagination settings, filter combination logic, side effects (none expected for list), rate limits, or response structure. Lacks transparency for safe usage.

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?

Single sentence with no unnecessary words. Efficiently conveys core functionality and key filtering options. Appropriate length for the tool's purpose.

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 7 parameters and no output schema, the description is too minimal. It does not explain pagination semantics, filter behavior (AND/OR), response format, error handling, or required permissions. Incomplete for a tool of this complexity.

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 mentions pagination, search text, client filters, and progress filters, mapping to 5 of 7 parameters, but omits includeDeleted and includeImported. Adds high-level meaning but lacks detail on each parameter's purpose or constraints.

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 lists service orders from 'D-Tools SI', specifying the resource and action. It mentions optional filters (pagination, search, client, progress), which distinguishes it from singular or creation tools.

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 implies usage for listing service orders with filters but provides no explicit guidance on when to use this tool versus alternatives like get_service_order or create_service_order. No when-not-to-use or contextual advice.

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