bulkUpdatePeople

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

Without annotations, the description discloses rate limits and return results per person, but lacks details on idempotency, partial failure behavior, authentication needs, or side effects. It is adequate but not comprehensive.

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 very concise: two sentences with no redundancy. The purpose is front-loaded in the first sentence, and additional details are succinct.

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 3-parameter tool with no annotations or output schema, the description covers purpose, rate limits, and return results. However, it lacks details on error handling, partial success scenarios, and specific field behaviors, making it somewhat incomplete.

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 description adds value by noting that updates are the same fields as updatePerson, providing context beyond the schema. Schema coverage is 100%, so baseline is 3, but the extra context elevates it.

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 clearly states it updates multiple people with the same changes, distinguishing from single-update sibling tools like updatePerson. The verb 'Update' and resource 'multiple people' are specific and action-oriented.

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 implies usage for bulk updates but lacks explicit guidance on when to use versus alternatives (e.g., updatePerson) or when not to use. It does mention rate limits, which provide operational context.

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