delete_growth

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

The description discloses a key behavioral trait: deletion is 'permanently' destructive, which is important for an agent to know. Since no annotations are provided, this description carries the burden. It doesn't mention potential side effects like cascading deletes or lack of undo, but the 'permanently' keyword adds some transparency 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 one sentence long, front-loaded with the action, and includes necessary guidance. Every word earns its place with no fluff.

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?

The tool is a simple delete operation with two parameters and no output schema, so completeness is moderate. The description explains the prerequisite for obtaining the entry_id, which is helpful. However, it doesn't describe what happens after deletion (e.g., success/failure) or whether child_uid is used for scoping, but given simplicity, it's adequate.

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 for parameter semantics. However, the description only mentions 'entry id' and not 'child_uid'. It provides some context for 'entry_id' but not for 'child_uid'. Baseline for 0 coverage would be low, but the description helps a bit, so a 3 is appropriate.

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 tool's action: 'Permanently delete a growth measurement.' This specifies the verb and resource, and distinguishes it from sibling tools like 'delete_diaper' or 'delete_sleep' by mentioning 'growth measurement.'

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 clear guidance on when to use it: after obtaining the entry id via 'get_growth_history' or 'get_latest_growth'. However, it doesn't explicitly say when not to use it or mention alternatives for deletion, but the context is clear enough.

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