Household Update Current User

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

Annotations already indicate readOnlyHint=false, destructiveHint=false. The description adds 'This may create or update Monarch data', hinting at potential creation. However, it does not disclose required permissions, side effects, or rate limits. The added context is minimal but non-contradictory.

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?

The description is extremely concise (two sentences) but at the cost of necessary detail. While no words are wasted, the structure does not provide front-loaded essential information for a mutation tool with multiple parameters. It is efficient but under-specified.

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?

Given the tool's complexity (5 parameters, no output schema, potentially creatable side effect), the description is inadequate. It lacks detail on what fields can be updated, the meaning of output modes, and the behavior of session_path. An agent would need additional context to invoke this tool correctly.

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 40% (2 of 5 parameters have descriptions). The tool description adds no parameter explanations. An agent cannot infer what 'timezone', 'display_name', or 'session_path' mean for updating a user. This fails to compensate for the low schema coverage.

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 title and description clearly state 'Update current user', which matches the tool name. However, it does not distinguish this tool from its sibling 'household_get_current_user' or explain that it may also create data. A specific verb and resource are present, but sibling differentiation is missing.

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?

No guidance on when to use this tool vs. alternatives (e.g., household_get_current_user for reading). No conditions, prerequisites, or when-not-to-use instructions are provided.

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