List Checklist List Created By Contact Filter Options

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it returns a JSON array and mentions pagination parameters, but does not disclose additional behavioral traits such as authorization requirements, rate limits, or response structure beyond the schema. With annotations covering the safety profile, the description adds minimal extra 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 moderately concise but includes redundant information like the API category and endpoint path, which may not be necessary for an agent. It front-loads the main purpose but could be trimmed to improve efficiency.

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?

For a simple filter options tool with good schema coverage and annotations, the description covers the essential information: purpose, output type, required parameter, and usage scenario. It is sufficiently complete for an agent to understand and use the tool correctly.

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 100%, so the baseline is 3. The description only restates that `project_id` is required and implies pagination via 'paginated overview', but does not add meaning or syntax details beyond the input schema.

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 contacts that have created inspections for filtering purposes. It specifies the output as a JSON array of available filter values and distinguishes from siblings by focusing on 'created_by_contact' filter options. The phrase 'enumerate Inspections' is slightly ambiguous but overall the purpose is clear.

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 usage context: 'Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' It mentions required parameter `project_id`. However, it does not explicitly state when not to use this tool or provide comparisons with sibling filter option tools, limiting guidance for selection.

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