edit_diaper

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Edit an existing' implying modification, but does not mention effects on existing data, permission requirements, idempotency, or failure behavior. For a mutation tool with no annotation support, this is a significant 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?

Two short, direct sentences with no wasted words. The first sentence states the purpose, the second gives the critical prerequisite. Excellent front-loading and structure.

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, 0% schema description coverage, and no output schema or annotations, a one-line description is grossly inadequate. It fails to explain the role of most parameters, the nature of the edit operation, or how to interpret results. This is a highly under-specified tool for its complexity.

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 coverage is 0%, so description must compensate. It adds meaning only to interval_id by instructing to get it from get_diaper_history. The other 8 parameters (mode, color, notes, start, etc.) are left undocumented, with only enum values providing partial clues. This minimal guidance is insufficient for a tool with many similar enum fields.

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?

Clearly states the tool edits an existing diaper or potty entry, and provides a hint about obtaining the interval_id. It distinguishes from other edit tools by naming the resource, though it doesn't explicitly contrast with delete_diaper or log_diaper.

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 explicit guidance to get the interval_id from get_diaper_history first, which is a necessary prerequisite. It doesn't mention when to avoid using this tool or alternatives, but the instruction is actionable enough for basic usage.

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