edit_food_entry

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

Annotations provide readOnlyHint=false and idempotentHint=true. The description adds the unchangeable date constraint and the prerequisite auth requirement, which are not covered by annotations. No contradictions.

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?

Three sentences with no waste: purpose statement, a critical constraint, and a prerequisite. Front-loaded with the core action, each sentence provides distinct 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 mutation tool with 5 parameters and no output schema, the description covers purpose, a constraint, and auth need. However, it lacks guidance on which optional parameters to use, error behavior, or idempotency implications, leaving gaps for the agent.

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 only 40%. The description does not explain any parameter semantics beyond what the schema provides. It mentions 'date' which is not a parameter, causing potential confusion. No added value for parameter understanding.

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 'Edit an existing food diary entry' with a specific verb and resource. Among siblings like create_food_entry and delete_food_entry, it clearly distinguishes the edit operation.

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 states the constraint 'Cannot change the date,' guiding against using this tool for date modifications. It also requires profile auth, but does not explicitly mention alternatives like using delete+create for date changes.

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