List Filter Options For Is Rejected

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON array and mentions pagination (page/per_page). It does not contradict annotations, but adds limited new behavioral context beyond the structured fields.

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 4 sentences, front-loaded with the main purpose. However, it includes extra details like 'Procore API: Project Management > Submittals' and 'Endpoint: GET /rest/v1.0/...' which may not be necessary for an AI agent, slightly reducing conciseness.

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, but the tool is simple (returns list of filter options). The description covers pagination and required parameter. Annotations provide safety profile. The description is reasonably complete for an AI agent to understand the tool's interface and behavior.

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% description coverage for all 3 parameters (project_id, page, per_page). The description mentions required parameters and pagination but does not add meaning beyond what the schema already provides, so baseline score of 3 applies.

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 explicitly states it returns all Filter Options for Is Rejected for the project, with a specific verb and resource. It differentiates from sibling filter option tools by naming the specific filter ('is_rejected') and context (Submittals).

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 indicates when to use it (enumerate Submittals, paginated overview, find IDs, filter by query) and required parameter. However, it does not provide explicit when-not-to-use guidance or mention alternatives among the many sibling filter options tools.

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