claimPerson

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Claim an unclaimed person', implying a state change, but does not reveal what claiming entails (e.g., assignment to current user), whether it fails if the person is already claimed, idempotency, or permission requirements. This is insufficient for a state-changing tool.

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 with no filler, clearly front-loading the purpose. It is appropriately sized for a simple one-parameter tool and every word earns its place.

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 tool with no annotations and no output schema, the description is too terse. It does not explain the effect of claiming, provide usage context, or clarify what the caller should expect. The one-line purpose leaves too much implicit for an AI agent to use it 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?

The schema already describes personId as 'Person ID to claim' with 100% coverage. The description adds no additional meaning about the parameter beyond the schema, so it meets the baseline of 3 but does not exceed 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 uses a specific verb 'claim' with a clear resource 'unclaimed person', which distinguishes it from siblings like createPerson, updatePerson, or listUnclaimed. It concisely conveys the action and target, making the tool's purpose immediately evident.

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 on when to use this tool versus alternatives. The description does not mention related tools like listUnclaimed, nor does it explain that claiming typically follows listing unclaimed people, and there are no exclusions or preconditions stated.

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