List Filter Options For Buffer Time

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON array and mentions the Procore API endpoint. No contradictions. It does not detail error conditions or rate limits, but with annotations it is adequate.

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?

Three sentences, front-loaded with the core purpose. No superfluous information. Efficient for a list tool.

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?

For a simple filter list tool, the description combined with annotations and full schema provides enough context. No output schema needed. The response format is implied (JSON array). Complete for the tool's complexity.

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 schema already documents all three parameters. The description only mentions project_id as required and the endpoint, adding no extra meaning beyond the schema. Baseline 3 is appropriate.

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 the tool returns all Filter Options for Buffer Time for a project, with use cases like enumerating Submittals, finding IDs, and filtering. It is specific to buffer_time but does not explicitly distinguish from sibling filter options tools, which are many (e.g., list_filter_options_for_location).

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 gives usage guidance: 'Use this to enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters.' It mentions the required project_id but does not provide when-not-to-use or compare to alternatives.

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