delete_feed

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

With no annotations provided, the description carries the behavioral disclosure burden. 'Permanently delete' clearly signals irreversibility, an essential trait for a delete operation. It also identifies the resource types covered, which is useful context beyond the schema.

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 two compact sentences with no filler. The primary purpose is front-loaded, and the prerequisite guidance is placed second for immediate procedural value.

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 two-parameter delete tool, the description covers the essential context: what is deleted, that deletion is permanent, which feed types are included, and how to obtain the key parameter. It could be marginally more complete by clarifying child_uid, but overall it is sufficient.

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 0%, so the description must compensate. It adds meaningful semantics for interval_id by explaining how to obtain it. However, child_uid is not explained at all, leaving that parameter fully dependent on its name and schema type.

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 ('Permanently delete') and the specific resource ('feed entry'), narrowed to nursing/bottle/solids. This distinguishes delete_feed from siblings like delete_diaper, delete_growth, and delete_pump.

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?

It provides a clear prerequisite: 'Get the interval_id from get_feed_history first.' This tells the agent how to obtain the required ID and implies appropriate sequencing. It does not explicitly enumerate when not to use the tool, but the context is strong.

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