removeTagFromPerson

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

With no annotations, the description takes on the burden of behavioral disclosure. It reveals the read-modify-write cycle and the guarantee of not affecting other tags, which adds meaningful context about how the operation works internally. Could disclose failure behavior but not necessary for a simple removal.

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?

Two sentences, front-loaded with the core purpose, followed by the key behavioral note. Every clause earns its place with no redundancy.

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 simple two-parameter tool with no annotations and no output schema, the description provides the essential behavioral context (single tag, non-destructive to other tags, internal cycle). It is sufficient for an agent to select and invoke the tool, though it doesn't specify edge-case outcomes.

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 covers both parameters with descriptive text (Person ID, case-insensitive match). The description adds no additional parameter-level meaning, so baseline 3 applies per high schema coverage.

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 ('Remove a single tag') with the specific resource ('from a person') and adds a distinguishing guarantee ('without affecting their other tags'). This distinguishes it from generic updatePerson operations.

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?

Implies usage for removing a tag from a person, but does not explicitly state when to choose this over updatePerson or other tag-related tools. No alternatives or exclusions mentioned.

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