List Checklist List Type Filter Options

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

Annotations already declare readOnlyHint, destructiveHint false, idempotentHint, openWorldHint. The description adds pagination and optional search behavior, but does not disclose any additional behavioral traits like rate limits or data freshness.

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 concise at 4 sentences, front-loads the main purpose, and avoids unnecessary details. However, it includes explicit API endpoint info which may be extraneous for some agents.

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?

No output schema, so description explains return format as 'JSON array of available filter values.' It mentions pagination and search but does not detail the structure of each filter value (e.g., id, name). Adequate but slightly vague.

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 baseline is 3. The description mentions required parameters and pagination/search, but these are already covered in schema descriptions. It adds minimal additional meaning beyond the 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 inspection types with pagination and optional search, and specifies it returns a JSON array of available filter values. However, it does not explicitly differentiate from other filter options tools in the sibling list, though the name implies it's for type filter options.

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: 'enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not mention when not to use this tool or suggest alternatives, leaving some ambiguity.

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