List Filter Options For Approvers

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

Annotations already cover readOnlyHint, idempotentHint, and openWorldHint. The description adds that it returns a JSON array of available filter values, but does not elaborate on auth needs, rate limits, or side effects. With annotations present, the description adds modest value beyond what is already declared.

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: purpose, usage guidance, required parameter and API reference. It is front-loaded, every sentence adds value, and there is no redundancy or filler.

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 states the return type (JSON array). With 100% schema coverage and annotations providing safety and idempotency, the description is complete enough for this simple read tool. Could include pagination behavior but is not necessary.

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?

The input schema has 100% coverage (all 3 parameters described). The description only reiterates that project_id is required, adding no new semantic meaning for the parameters. According to the rule, high schema coverage provides a baseline of 3, and the description does not enhance it.

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 Approvers for the project, specifying the resource (Submittals) and the purpose (enumerate, find IDs, filter by query parameters). It distinguishes from sibling tools by explicitly mentioning 'for Approvers' and the API endpoint path.

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 usage context: 'Use this to enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not list exclusions or alternatives, but the context is clear given the sibling set focuses on different filter options.

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