complete_reminder

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

Beyond annotations (idempotentHint=true, readOnlyHint=false), the description adds specific state changes (STATUS, PERCENT-COMPLETE), though it does not detail other behavioral aspects like side effects on related items.

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?

Single sentence with essential details front-loaded. The parenthetical addition adds precise status changes without extra verbiage. Every word earns its place.

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?

Adquate for a simple write operation with output schema present, but lacks parameter explanations and usage guidance. With only 2 params and 0% schema coverage, more parameter context would improve completeness.

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 coverage is 0%, but the description provides no explanation of the 'uid' and 'list' parameters. The agent cannot infer the meaning or required format from the description alone.

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 clearly states the action: 'Mark a reminder complete' with specific status fields (STATUS:COMPLETED, PERCENT-COMPLETE:100), distinguishing it from siblings like update_reminder which would modify other fields.

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?

Implied usage for completing reminders, but no explicit guidance on when to use this tool vs siblings like update_reminder or delete_reminder. Does not mention prerequisites or when not to use.

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