pumping_create_pumping

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

With no annotations, the description must carry the burden of behavioral disclosure. 'Record a pumping session' implies persistence but does not state side effects, visibility, idempotency, or whether timer_id replaces start/end times. For a create operation, this is a notable gap.

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 very short and free of fluff, but it is under-specified. It essentially restates the tool name with a synonym; it is concise but lacks useful detail that would make the brevity valuable.

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?

Although the schema is rich and complete for parameter descriptions, the tool description omits important context, such as how timer_id interacts with the required start/end fields. This ambiguity could lead an agent to submit conflicting values. The description does not fill any gaps left by the structured fields.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-level meaning, but the schema already explains child_id, start, end, amount, notes, and timer_id. No additional compensation is needed.

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 uses the specific verb 'Record' with the clear resource 'a pumping session', which distinguishes this create operation from sibling tools like pumping_update_pumping, pumping_delete_pumping, and pumping_list_pumping. It unambiguously states the tool's core function.

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 alternatives. It does not mention when a pumping creation is appropriate, how it differs from feeding operations, or when to prefer pumping_update_pumping. The only usage hint is inside the child_id parameter description ('Use list_children to get IDs'), which is not in the tool description itself.

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