List FFXIV chores with reset-window status, filtered by character or category (gc_turnin, duty_support, beast_tribe, item_turnin, custom) to see what is due or overdue.
List chores and their reset-window status. Optional filters: character, category (gc_turnin, duty_support, beast_tribe, item_turnin, custom).
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | ||
| character | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. "List" implies a read operation and reset-window status hints at returned state, but it does not cover permissions, pagination, completion filtering, or other operational behavior.
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 definition is two efficient sentences with the core action front-loaded and no wasted wording. The filter details are compactly presented.
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 simple two-parameter list tool, it is adequate but not complete: there is no output schema, no annotations, and the description does not explain the return shape or how list_tasks differs from list_resets. The category enum detail helps, but the character filter remains underspecified.
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 0%, so the description must add parameter meaning. It does list the category values, which the schema omits, but it says nothing useful about the character filter beyond repeating its name.
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 uses a specific verb and resource: "List chores and their reset-window status." It is clearer than the bare name, but it does not explicitly distinguish this tool from the sibling list_resets tool.
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?
It mentions optional filters but gives no guidance on when to use this tool versus list_resets or list_characters. There are no exclusions or decision rules for choosing among the list siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.