Checklist Schedule Equipment Filter Options

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds that it returns a JSON array and the required parameter project_id, but does not elaborate on error handling, rate limits, or authentication beyond what annotations imply.

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?

Concise front-loaded description: starts with purpose, then usage, output format, required params, and API reference. No unnecessary words, every sentence adds value.

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 read-only filter tool, the description is complete: it specifies purpose, usage, output format (JSON array), required parameter, and full API endpoint. No output schema needed description clarifies return type sufficiently.

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 has 100% coverage, so baseline is 3. Description only reiterates the required project_id parameter, adding no new semantic information about page or per_page beyond what the schema provides.

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?

Clearly states it returns equipment associated to inspection schedules and is used to populate a filter UI. Differentiates from siblings by specifying the resource (equipment) and its association to inspection schedules.

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?

Explicitly says 'Use this to populate a filter UI', providing clear context for invocation. Does not explicitly state when not to use or mention alternatives, but the sibling tools are clearly for different filter entities, making the use case obvious.

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