List Company Checklist Templates

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds value by specifying pagination behavior (page, per_page, metadata) and filtering capabilities, which are not covered by annotations. No contradictions.

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 relatively concise at four sentences. It includes essential information but repeats the concept of returning items and provides API endpoint details that may be useful. Could be slightly tighter by avoiding repetition of 'pagination' and 'Inspections'.

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?

There is no output schema, so the description should describe the return structure. It mentions a paginated JSON array and pagination metadata, but does not detail the fields of each template item (e.g., id, name, inspection_type). The inconsistent use of 'Inspections' vs 'Templates' also undermines completeness. Given the tool's complexity (10 parameters, no output schema), the description is adequate but not thorough.

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?

The input schema has 100% coverage with detailed parameter descriptions, so the baseline is 3. The description highlights the required 'company_id' and pagination parameters but does not add significant new semantics beyond what the schema already provides.

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 returns Company Checklist Templates for a specified Company and explains its use for enumeration, filtering, and pagination. However, it inconsistently refers to 'Inspections' (e.g., 'Returns a paginated JSON array of Inspections'), which may confuse the agent about whether the tool returns templates or inspections. This reduces clarity.

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 provides context on when to use the tool (enumerating inspections, finding IDs, filtering) and mentions pagination controls. However, it does not explicitly distinguish this tool from siblings like 'list_checklist_templates' (likely project-level) or state when not to use it, leaving room for ambiguous selection.

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