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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds substantive behavior: it discloses the rotation algorithm (even weekly points, chores moving each week, rules and minimum ages honored), the concrete artifacts produced (printable PDF, one week per page, plus an .ics with one weekly summary per person), and the points/spread summary. That is real value beyond the structured fields.

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?

Front-loaded with the trigger list, then capability detail, then exclusions — a sound order for a 10-parameter tool. It is a single dense paragraph whose parentheticals run long, but essentially every clause carries routing or expectation-setting information, so little is wasted.

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 complex 10-parameter generator with an output schema and full annotations, the description supplies the missing conceptual layer: what the rotation guarantees, what files come out, and what the tool refuses to do. It doesn't explain defaults or interactions for parameters like weeks, start_date or layout, but those are documented in the schema, so nothing an agent needs to call it correctly is absent.

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 100%, including enums-in-prose for style, layout, paper and detailed examples for chores, rules, people and age_appropriate, so the description cannot add much parameter-level detail. Its only incremental semantics are behavioral — that rules and minimum ages are actually respected during assignment and that points are balanced across people — rather than per-parameter meaning.

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?

States a specific verb (generate) and resource (chore chart) and enumerates the trigger phrasings an agent will actually encounter ('chore chart for kids', 'roommate chore schedule', 'chore rotation or reward chart'). The scope is unmistakably different from generate_habit_tracker, so an agent can route between the two on name plus description alone.

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?

Opens with an explicit 'Use this when the user wants...' trigger list, and the closing sentence carves out three negative cases (no splitting one chore across days, no completion tracking, no reminders) that tell an agent when to look elsewhere. It stops short of naming a concrete alternative tool, so routing beyond the sibling is left implicit.

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