List Filter Options For Submittal Response

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral context beyond annotations by stating it returns a JSON array and implying paginated results via page/per_page parameters. No contradiction with annotations.

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 three sentences long, each earning its place: purpose, usage, and return format/endpoint. It is front-loaded and contains no wasted words.

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 no output schema, the description mentions it returns a JSON array of available filter values, which is helpful. It does not describe the structure of the array, but for a simple filter options tool, it is fairly complete. Could be improved by detailing the array's keys.

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 only mentions 'Required parameters: project_id' which is already in the schema. It does not add meaning beyond the schema, so baseline score of 3.

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 it returns all Filter Options for Submittal Response, with specific verb and resource. It explains usage for enumerating submittals, finding IDs, or filtering. However, it does not explicitly differentiate from many similar filter option tools among siblings, though the resource is uniquely identified.

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 explicit use cases: 'enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters.' This gives clear context for when to use the tool, but it does not mention when not to use it or provide alternatives, which is acceptable for a filter options tool.

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