List Checklist Schedule Assignee Filter Options

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds that the tool returns a JSON array with pagination and search capabilities, and states the endpoint. This is useful context beyond annotations, but the behavioral core is well-covered by annotations.

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, with no superfluous words. It front-loads the purpose and includes essential details (pagination, search, return type) and a note on the API source. Every sentence 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?

Without an output schema, the description explains that it returns a JSON array of available filter values. It includes the endpoint and key features (pagination, search). It does not mention sorting or default pagination limits beyond what the schema provides, but for a simple read tool, it is largely complete.

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 description coverage is 100%, so all parameters are documented structurally. The description highlights required parameters (company_id, project_id) and mentions pagination and search, which adds a bit of usage context, but does not add significant new 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 assignees of the checklist schedule with pagination and search, and mentions enumeration of Inspections. It provides a specific verb and resource, but does not explicitly differentiate from sibling filter tools like location or equipment, preventing a top score.

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 gives concrete use cases: 'use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' This is helpful context, but it does not mention when not to use or directly compare to alternative tools.

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