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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond them — it doesn't say whether the output is a deterministic assignment, whether randomness is used (which would undercut the idempotent claim in spirit), or whether the split is even. "Client and server side" is noise rather than behavioral disclosure.

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?

It is a single short sentence, so there is no bloat to trim, but roughly half of it ("client and server side from freedailypro") is filler the agent cannot act on. The useful part, the chore-splitting purpose, is present but under-developed rather than front-loaded with detail.

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 two-required-array tool with no output schema and zero parameter documentation, the description should explain both the input shape and what kind of result comes back. It does neither, so an agent cannot predict the response format (e.g., a mapping of person to assigned chores) or the distribution rule.

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 0% for both required array parameters, so the description carries the full burden — and it provides none. It never explains that "people" are the recipients, that "chores" are the items being distributed, or how the two arrays are matched (one-to-one, round-robin, by count). Only the self-evident field names give the agent any hint.

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?

"Household chore splitter" does convey a specific resource and an implied verb (splitting chores among people), which separates it from most siblings in the planning_ family. But the trailing "client and server side from freedailypro" is opaque vendor jargon that adds no operational meaning and muddies what the tool actually returns.

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?

There is no guidance on when to use this rather than the adjacent planning_grocery_list or planning_split_bill tools, nor any statement of preconditions (e.g., must chores and people be non-empty). The agent is left to infer everything from the name alone.

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