Advanced: create XMemo legacy reminder

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

The description does not disclose behavioral traits beyond what annotations already indicate. While annotations show readOnlyHint=false (write operation) and destructiveHint=false, the description merely restates 'Create' which is already implied by the schema and annotations. No additional context (e.g., side effects, permissions, or limits) is added.

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 a single sentence, which is concise and front-loaded. It avoids unnecessary details, though it could be slightly longer to add usage guidance without losing conciseness.

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?

Given that this is an alias tool with 5 parameters and an output schema, the description is too minimal. It does not explain how parameters like 'due_at' and 'scope' relate to creating a TODO reminder, nor does it cover return values or edge cases. The description alone is insufficient for an agent to fully understand the tool's behavior.

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 100%, with all 5 parameters having descriptions. The description does not provide any additional meaning beyond what the schema already conveys, so it meets the baseline without adding value.

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 verb ('Create') and the resource ('a TODO item') and identifies itself as an alias for 'create_memory_todo', making the purpose unambiguous. The title 'Advanced: create XMemo legacy reminder' is secondary and does not detract from clarity.

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?

No guidance is provided on when to use this tool versus its alias 'create_memory_todo' or other sibling tools. There is no 'when-to-use' or 'when-not-to-use' information, leaving the agent without context for selection.

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