list_canned_services

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

No annotations provided, so description carries full disclosure burden. Adds valuable domain context that these are reusable templates for work orders, indicating their purpose. However, omits behavioral details like pagination limits, caching behavior, or whether results are static/frequently updated.

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?

Two tightly constructed sentences. First sentence establishes action and resource; second sentence adds critical domain context (reusable, for work orders). Zero redundancy, every word earns its place.

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?

Adequately complete for a simple list operation. Explains the business concept ('canned' means pre-built templates), which is essential given the jargon. Lacks output format details, but given no output schema exists and params are well-documented, this is acceptable.

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?

Input schema has 100% description coverage (locationId, limit, page all documented). Description provides no additional parameter-specific semantics, but with complete schema coverage, baseline score 3 is appropriate as no compensation is needed.

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?

Strong specific verb ('List') with clear resource ('pre-built canned service templates'). Effectively distinguishes from sibling 'get_canned_service' (singular vs plural) and from 'list_services' by clarifying these are reusable templates rather than active service records.

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?

Provides implied usage context by stating templates 'can be added to work orders,' suggesting when these are needed. However, lacks explicit guidance on when to choose this over 'list_services' or other alternatives, and includes no 'when not to use' exclusions.

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