List Checklist List Inspector Filter Options

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

Annotations (readOnlyHint=true, idempotentHint=true) already indicate safe read behavior. The description adds that it returns a JSON array of filter values, but the statement 'enumerate Inspections when you need a paginated overview' is potentially misleading because the endpoint returns filter options, not the inspections themselves. This inconsistency harms transparency.

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 compact (four sentences) and front-loads the action. It includes endpoint info and required parameters. However, the sentence about enumerating inspections is slightly off-topic and could be rephrased for clarity.

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 the simple nature (3 parameters, no output schema, safety annotations), the description covers core purpose and output type. However, it does not explain that the result is a list of possible inspector values (e.g., names/IDs) to be used as query filters, leaving a gap in how the output is consumed.

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 description's mention of required project_id adds no new meaning. It does not elaborate on the semantics of page and per_page parameters beyond what the schema already provides. Baseline score of 3 is appropriate.

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 inspector filter options for inspections, specifies the endpoint, and notes it returns available filter values. However, the phrasing 'enumerate Inspections' could mislead an agent into thinking it returns inspections themselves, not filter options. It distinguishes from siblings only by naming, but without explicit differentiation.

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 advises using this tool for a paginated overview, finding IDs, or filtering by query parameters. It also states the required parameter (project_id). However, it does not mention when not to use it nor compares it to alternative filter option endpoints (e.g., by location, type, etc.), leaving selection guidance incomplete.

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