updatePerson

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

No annotations are provided, so the description carries full burden for behavioral transparency. It only states 'Update' which implies mutation, but does not disclose side effects (e.g., whether partial updates are supported, required permissions, idempotency, or error conditions). The description adds minimal behavioral context beyond the action.

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; it is concise but lacks structure. It does not front-load critical information beyond the basic action. Every word earns its place, but the description is too minimal to be considered well-structured for an 18-parameter tool.

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 complexity of 18 parameters and no output schema, the description is incomplete. It does not explain return values, error handling, or the behavior of partial updates. The schema covers parameter details, but the overall tool context is under-specified.

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 has 100% coverage with descriptions for all 18 parameters. The tool description does not add any additional meaning beyond what the schema already provides. Baseline 3 is appropriate since the schema handles parameter semantics adequately.

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 'Update an existing person in FUB' clearly specifies a specific verb (Update) and resource (existing person in FUB). It distinguishes itself from sibling tools like createPerson or deletePerson, which have different actions. The purpose is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it does not mention that this tool requires an existing person ID (implied by 'existing'), nor does it contrast with bulkUpdatePeople or createPerson. Usage context is absent.

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