reminders_complete_task

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

Annotations already declare write, idempotent, and non-destructive behavior, so the description only needs to add context. It contributes the return contract ('return saved record') and the required permission scope, but says nothing about the human-approval path implied by the _approvalId parameter or how idempotency keys must be reused.

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 short clauses with the action front-loaded and no filler; the trailing version/permission tag is compact. It is appropriately sized, though the bracket tag is boilerplate rather than informative.

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 output schema covers return values and the annotations cover the safety profile, so those gaps are excused. What remains missing is the toggle direction of `completed`, the relationship to reminders_update_task, and any note on the approval workflow for a write tool.

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 75%, so the schema already documents id, _approvalId, and _idempotencyKey. The phrase 'completion state' loosely maps to the bare `completed` boolean (the one undocumented parameter), but it never clarifies that setting it false reverses completion, which is the key semantic ambiguity.

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 and resource ('Set a reminder completion state') plus the return behavior ('return saved record'), so the agent knows exactly what operation runs. It does not, however, distinguish itself from the sibling reminders_update_task, which could plausibly also set a completion field.

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?

There is no when-to-use guidance, no indication that completed=false is how you un-complete a task, and no mention of when to prefer this over reminders_update_task or reminders_delete_task. The agent must infer the routing decision entirely from the name.

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