list_intervals

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

With no annotations, description discloses key behaviors: grouping, paging, and maximum range. It gives meaningful operational context beyond just saying 'list intervals'. Could be richer but sufficient for a read-only listing tool.

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?

Two concise sentences front-loaded with purpose and paging detail. Every word earns its place with no waste.

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 9 parameters, no output schema, and no annotations, the description gives the core behavioral model (grouped, paged, max range). It's adequate for a developer to infer usage, though a bit more on period vs from/to interaction would push it higher.

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 already provides 100% coverage for all 9 parameters. Description adds context about 'max 100 days' and 'paged by day' that ties into from/to and page/size, enhancing understanding without duplicating schema details.

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?

Description clearly states the tool lists raw time entries (intervals) grouped by day for a date range, with a specific verb and resource. The 'raw' qualifier distinguishes it from sibling tools like time_report or log_interval.

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?

Provides clear usage context: date range limited to 100 days and paging by day. Does not explicitly mention alternatives or when not to use, but the distinction from siblings is implied by 'raw'.

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