List Filter Options For Lead Time

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

Annotations already declare readOnlyHint=true and destructiveHint=false, providing a safety profile. The description adds useful behavioral context: returns a JSON array, requires project_id, and specifies the API endpoint. 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, front-loaded with purpose. It includes all essential information without any fluff. Every sentence adds value: purpose, usage, API details.

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 but rich annotations, the description covers purpose, usage, endpoint, required parameters, and return type. It is complete for a simple filter listing tool.

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 the baseline is 3. The description mentions project_id as required but does not add meaning for page or per_page beyond the schema. No extra value provided.

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 filter options for Lead Time for a project. It explains the specific use cases: enumerating submittals with pagination, finding IDs, and filtering by query parameters. It distinguishes itself from sibling filter tools by specifying 'lead time' in the name and description.

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 tells when to use this tool (enumerate submittals, paginated overview, find IDs, filter) but does not explicitly mention when not to use it or provide alternatives. Given the simplicity of the tool and the context of many siblings, the guidance is adequate for the AI agent.

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