List Checklist List Equipment Filter Options

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it returns a JSON array. However, it does not explain pagination behavior despite page/per_page parameters in the schema. No additional context on rate limits or authentication beyond the endpoint reference.

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?

Description is relatively short and front-loaded with purpose. Some redundancy with the title and the inclusion of API details (Procore category, endpoint) which may be noise but do not severely detract. Could be slightly tighter.

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 exists, so the description's note 'Returns a JSON array of available filter values' is helpful. However, it does not describe the structure of array items (e.g., fields like id, name). Missing details on potential errors or empty results. Adequate but incomplete for a filter options tool.

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?

Input schema has 100% coverage with descriptions for all 3 parameters. The description only mentions project_id as required and implies pagination via 'paginated overview'. It adds minimal new meaning beyond the schema, meeting the baseline for full schema coverage.

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 states it lists equipment filter options for inspections, which is clear. However, it says 'enumerate Inspections' which is slightly misleading since it returns filter values, not inspections directly. The verb-resource combination is specific and distinguishes from siblings by name.

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?

Provides context about when to use (paginated overview, find IDs, filter by query) and notes required project_id. But no explicit guidance on when not to use or comparison with sibling filter option tools (e.g., inspection_type, location). Limited differentiation.

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