Checklist Schedule Location Filter Options

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which the description aligns with by stating it returns data. The description adds that it returns a JSON array and provides the endpoint, but does not go beyond annotations to disclose rate limits, auth, or pagination details. 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 concise but includes some repetition: 'Returns locations...' is restated as 'Returns a JSON array...'. The API endpoint and category are useful but could be considered extra. Overall, it is adequately sized but not optimally streamlined.

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 that the schema covers all parameters, annotations cover safety, and there is no output schema, the description provides the output format (JSON array) and usage context (populate filter UI). It lacks details on pagination behavior beyond the schema, but for a simple filter tool this is sufficient.

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 the schema already documents all three parameters. The description only mentions 'Required parameters: project_id' which duplicates the schema. It adds no 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 that the tool returns locations for inspection schedules and is used to populate a filter UI. It distinguishes itself from sibling filter tools by specifying 'locations' as the returned resource. The verb 'Returns' and the resource 'locations' are specific.

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 context for use ('populate a filter UI with valid values for Inspections') and specifies the required parameter 'project_id'. It does not explicitly exclude when not to use it or list alternatives, but the purpose is clear enough for an agent to decide.

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