time_buckets

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

No annotations exist, and the description provides no behavioral context. It doesn't disclose whether the operation is read-only, any rate limits, pagination, or output format, leaving the agent to infer everything.

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 short and includes an example, but it's structurally awkward ('Data · query timeBuckets. Variables: filter. Example variables: ...'). It's concise but lacks a clear, organized explanation.

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?

The tool has a complex filter and no output schema, yet the description provides no explanation of what the query returns or what time buckets represent. The example helps but is insufficient for an agent to understand the tool's full scope.

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 schema descriptions for 'filter' are purely type-based ('GraphQL: TimeBucketsFilter!'), so the description's example JSON adds real value by revealing the structure: 'by', 'startTime', 'endTime', and 'query'. This gives concrete guidance for constructing the filter, even though field semantics aren't fully explained.

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 says 'Data · query timeBuckets' which is vague and largely restates the tool name. It doesn't explain what a time bucket is, what the query returns, or how it differs from other query tools like 'graphql_query'.

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?

No guidance is provided on when to use this tool versus alternatives. The example filter includes an incidentId and time range, hinting at a possible use case, but no explicit conditions or exclusions are stated.

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