List Available Submittal Filters

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

Annotations already indicate readOnly, non-destructive, idempotent. The description adds pagination details (page, per_page, metadata) and the API endpoint, which supplement the annotations effectively.

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 verbose and repetitive, starting with an unclear statement about 'endpoints for specific filter options' before clarifying it returns Submittals. Could be condensed to one or two clear sentences.

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 name implies accessing filter options, the description fails to explain what filters are available or how to use them. No output schema exists, so the description must clarify the response, but it contradicts itself by mixing filters and submittal listing.

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%, so description adds little beyond reinforcing page/per_page usage. The mention of control over pagination is helpful but not essential given schema descriptions.

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 endpoints for filter options, but then says it returns a paginated array of Submittals, creating confusion between listing filters and listing submittals. The name suggests filter options, yet the description focuses on enumerating Submittals, leading to a mismatch.

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 provides some guidance on when to use the tool (e.g., for paginated overview, finding IDs, filtering), but lacks explicit exclusions or comparisons to sibling tools like list_submittals. It mentions required project_id but no alternative scenarios.

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