reminder_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation is known. The description adds the specific effect: 'reminderAt cleared' and 'Returns the updated tracked job', giving concrete behavioral context beyond the annotations. There is no contradiction with annotations.

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 two compact sections plus a one-sentence summary. It front-loads the purpose, then details input and output in a structured list. Every sentence is necessary and no redundancy is present.

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 one-parameter destructive tool with a clear output schema and existing annotations, the description covers the essential input nuance (ID distinction) and the result (updated tracked job). Minor omissions such as idempotency or error behavior are acceptable given the richness of the output schema and annotations.

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 single parameter's description in the schema is identical to the tool description's input section, so no extra meaning is added beyond the schema. With 100% schema description coverage, the baseline is 3 and no bonus is warranted.

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 opening sentence 'Deletes a reminder from a tracked job' clearly identifies the action (delete) and resource (reminder from a tracked job). This distinguishes it from siblings such as reminder_set (which presumably creates/updates) and tracker_remove (which would remove the entire tracked job).

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 provides no explicit when-to-use guidance or alternatives. It does clarify which ID to use ('tracked_job_id... distinct from trackable.id and job.id'), but that is parameter-level, not usage guidance. The intended usage is only implied by the verb 'deletes' and sibling tool names.

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