mfp_delete_exercises

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

The description openly discloses that the action deletes all exercise entries on a date, which is important destructive behavior. This aligns with the annotations (destructiveHint=true, readOnlyHint=false). It adds the useful warning that the deletion is scoped to an entire day's entries, not just one selected entry.

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 main description is one compact, front-loaded sentence with no filler. The '[legacy]' flag is a meaningful addition rather than noise, and the resource-action-scope structure makes the intent immediately scannable.

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 destructive tool, the description plus annotations are mostly sufficient: the action, scope, and destructive nature are clear, and the output schema covers return expectations. The only noticeable gap is that it does not explicitly mention irreversibility, but destructiveHint=true already communicates this.

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?

The input schema already documents the date format and default ('YYYY-MM-DD', defaults to today) and the response_format enum with its markdown/json choices. The description's reference to 'date' is consistent but does not add meaningful parameter detail beyond the schema.

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 a specific verb and resource: 'Delete all exercise entries logged on a date.' It clearly identifies scope (all entries, not a single entry) and differentiates the tool from sibling tools like mfp_delete_meal or mfp_delete_custom_food. The subject matter is immediately obvious from the text.

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 implies usage: use this tool when you want to remove every exercise entry for a specific day. However, it does not explicitly state when not to use it, and the '[legacy]' marker hints that the tool may be deprecated without naming a successor or alternative.

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