List Filter Options For Created Via

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON array and supports pagination via page and per_page parameters. It does not contradict annotations and provides additional context on data format and pagination.

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, consisting of a few sentences. It is front-loaded with the main purpose. Some extra information (Procore API, endpoint) is included but does not detract significantly.

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 the tool's simplicity (filter list), good annotations, and full schema coverage, the description covers what it returns, the required parameter, and usage context (Submittals, pagination). It is adequately complete for agent understanding.

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% with descriptions for all three parameters. The description mentions required parameter project_id but adds no extra meaning beyond the schema. Baseline is 3 for full 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 clearly states the tool returns 'all Filter Options for Created Via' for a project, specifying it is for Submittals. The verb+resource is specific and distinct from siblings, which are other filter option tools.

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?

It says 'Use this to enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters.' This gives context on when to use, though it does not explicitly exclude alternatives or describe when not to use. The guidance is clear but could be more comprehensive.

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