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 covered. However, the description adds nothing beyond that — not even the splitting policy (random assignment, fair distribution, round-robin), which is the core behavioral trait an agent would need. It does not contradict annotations.

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?

Three words is technically concise, but this is under-specification rather than efficient structure — there is no front-loaded explanation of behavior or output. Brevity here costs the agent necessary 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?

With no output schema, two undocumented required parameters, and no explanation of the splitting algorithm or return shape, the description leaves an agent unable to predict what happens when the tool is invoked. It is inadequate for even a simple two-parameter tool.

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% for both required parameters, so the description must compensate and does not. It never clarifies that "people" is a list of names or that "chores" is a list of task strings, or whether list lengths must match.

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" identifies the domain (chores) and an implied action (splitting), but it is a noun fragment with no explicit verb and no statement of what the tool returns or how it splits. It does not differentiate itself from nearby siblings like planning_split_bill or planning_grocery_list.

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 about when to call this versus alternatives, no prerequisites, and no mention of the sibling tools it might be confused with. An agent must infer everything from the name.

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