updateAutomationPerson

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

With no annotations, the description must disclose behavioral traits. It only states 'Update' without mentioning idempotency, permissions, side effects, or result behavior, leaving the agent uninformed about mutation consequences.

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 a single sentence of six words, front-loaded with action and resource. It is appropriately sized for the tool's simplicity and contains no wasted words.

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?

Despite full param coverage, the description lacks explicit return values, error conditions, or behavioral context. For a mutation tool with no annotations and no output schema, it falls short of being complete.

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?

The input schema fully documents both 'id' and 'status' with descriptions, so the baseline is 3. The description does not add parameter semantics beyond saying 'person's automation status', which is already implied by the tool name and schema.

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 uses a specific verb ('Update') and resource ('a person's automation status'), clearly distinguishing it from sibling tools like addPersonToAutomation or getAutomationPerson. It concisely conveys the tool's exact function.

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 is provided about when to use this tool versus alternatives such as 'addPersonToAutomation' or 'updateActionPlanPerson'. There are no prerequisites, exclusions, or context hints to help the agent choose this tool.

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