Chores List Tool

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

No annotations are provided, so the description carries the full burden. It states the tool 'lists' chores, implying a read-only operation, and specifies the output includes IDs and next scheduled time. However, it does not mention whether it returns only incomplete chores or includes details dependencies, but the core behavioral transparency is adequate.

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 concise, two sentences, front-loading the key output (IDs and next scheduled time) and then providing a usage hint. No inflated text.

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 zero parameters and an output schema (which likely documents the return fields), the description is complete for an agent to call and understand the result. It does not specify any filtering or sorting flags, but those are absent from the schema, so nothing is missing.

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 tool has zero parameters, and the description explicitly states 'List all chores' with no parameters needed. Since there are no parameters, the description need not explain them; this is effectively a perfect match for the schema.

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 states a clear verb and resource: 'List all chores with their IDs and next scheduled execution time.' It is distinguishable from sibling tools such as chores_overdue_tool (which likely lists only overdue chores) and chore_execute_tool (which executes a chore). The purpose is specific and unambiguous.

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 includes a second sentence: 'Use this to see what chores exist and when they are due next,' which provides a use case. However, it does not explicitly state when not to use this tool or mention alternatives like chores_overdue_tool for overdue filtering, so some inference is required.

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