list_chores

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

Adds context about return fields and detail_level behavior beyond schema. However, with no annotations, it omits authorization needs and other behavioral traits. Adequate but not comprehensive.

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 concise sentences covering purpose, options, and detail_level behavior. No unnecessary information.

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?

Covers key aspects: listing, filters, fields returned, and detail_level. No output schema, but description plus schema together provide sufficient completeness. Missing potential details like pagination or ordering, but acceptable.

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 descriptions. Description adds clarifying context: default for detail_level, purpose of filters. Enhances understanding beyond 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?

Explicit verb 'List' and resource 'chores' with scope 'all'. Distinguishes from sibling tools like get_chore (singular) and complete_chore (action).

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?

Provides clear context for using filters and detail_level. Does not explicitly state when not to use or mention alternatives, but sibling names imply singular use cases.

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