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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is largely covered. "Proposes only" adds genuinely useful context — that the call stages rather than finalizes the owner change — but the description never explains what a proposal record is, whether it requires later confirmation (confirm_change/discard_change), or what happens to an existing owner. There is also mild tension between "proposes only" and destructiveHint=true that the description leaves unexplained.

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 very short sentences, front-loaded with the action and its key qualifier. The second sentence largely restates the first, but it does emphasize the non-committal nature, so the redundancy is defensible rather than wasteful.

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 state-changing tool with destructiveHint=true, no output schema, a nested parameter, and low schema coverage, the description is thin. An agent cannot tell what a proposal does downstream, whether it is reversible, or what the parameters must reference, all of which matter for correct invocation.

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 only 33%, so the description is expected to compensate, and it adds nothing about task_id, owner_id, or additional_information. It does not even clarify that owner_id must be a household member, which is the key semantic constraint for this tool.

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 specific verb+resource ("assigning a task to a household member") and qualifies it as a proposal, so an agent knows the tool does not commit the assignment. It does not, however, distinguish itself from the very similar siblings suggest_task_owner and propose_task_reassignment, which an agent could easily confuse with this one.

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 explicit guidance on when to use this instead of suggest_task_owner, propose_task_reassignment, update_task, or complete_micro_action. The only usage signal is the terse "Proposes only", which implies a human confirmation step but never says so or names an alternative.

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