Add Tag Instance To Person

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

The description adds that the tool creates a record and returns it on HTTP 201, aligning with the POST endpoint. Annotations already indicate readOnlyHint=false, so the description confirms the create behavior but adds no further behavioral traits like permissions or side effects.

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 front-loaded with the action but contains redundancy and a grammatical error ('Resource Planning records' repeated). It could be more concise by removing the misleading reference and focusing solely on the tag instance operation.

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 no output schema, the description mentions the return object but lacks details on preconditions (e.g., tag must exist), error handling, or behavior when duplicate tags are added. The optional expr_date parameter is not explained.

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 coverage is 100%, fully describing all four parameters. The description merely lists the required parameters (company_id, person_id, tag_id) without adding any semantic context beyond the schema. No mention of the optional expr_date parameter.

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 the action 'Add Tag Instance to Person' and the resource, but the confusing reference to 'Resource Planning records' slightly muddles the purpose. It does not differentiate from sibling tools like remove_tag_instance_from_person, but the name itself is descriptive.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'Use this to create a new Resource Planning records' is vague and does not contrast with related tools. No when-not-to-use advice is given.

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