list_pump_intervals

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

With no annotations provided, the description is the sole source of behavioral details. It implies a read operation but does not explicitly state it is non-destructive, nor does it disclose any side effects, pagination, or ordering behavior. The agent lacks critical safety and operational context.

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 a single, succinct sentence (5 words) with no unnecessary words. This is highly efficient, though the brevity borders on underspecification. Nonetheless, it earns a high score for 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?

Given the lack of annotations, output schema, and parameter descriptions, the one-line description is grossly insufficient. It fails to cover return format, pagination, or relation to sibling tools, leaving the agent with minimal actionable context.

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 input schema has two parameters with 0% description coverage. The description does not explain the meaning or purpose of 'child_uid' or 'limit', nor does it hint at their usage. For a tool with no schema descriptions, the description should compensate but does not.

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 action ('retrieve') and the resource ('pump sessions for a child'), making the tool's purpose understandable. The name 'list_pump_intervals' aligns well with the description, though the term 'sessions' slightly differs from 'intervals'.

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 provides no guidance on when to use this tool versus sibling tools like 'log_pump' or 'edit_pump'. There is no mention of context or alternatives, leaving the agent to infer usage from the name alone.

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