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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered structurally. The description adds a useful scope boundary (no record deletion), but says nothing about what existing values get overwritten, reversibility, or required permissions for a 10-parameter write.

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 tight sentences, front-loaded with the action and followed immediately by the scope boundary. No filler or restatement of the title.

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 destructive 10-parameter mutation with 20% schema coverage, the description is far too thin: it doesn't clarify whether vehicleId/trackerId identify the target record, whether fields are partial-update or full-replace, or how doneDate/intervalType interact. The existing output schema excuses it from explaining return values, but nothing else compensates.

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 20% across 10 parameters, and the description contributes zero parameter meaning — it never mentions name, dueDate, doneDate, intervalType, or the identifiers. With only vehicleId/trackerId required and eight fields (including two enums) undocumented in the description, the parameter burden is largely unmet.

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?

States a specific verb (Edits) and resource (a TuneWorks maintenance reminder or service item), so the agent knows this mutates an existing maintenance record. It doesn't explicitly name siblings like complete_maintenance, archive_maintenance, or create_maintenance, so differentiation is left partly to inference.

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?

'Deletes are not supported' functions as a partial when-not hint, implicitly routing deletion to a sibling such as archive_maintenance. However, there is no positive guidance on when to use this versus complete_maintenance (marking service done) or create_maintenance (adding new items), leaving the choice implied.

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