add_tag

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

No annotations are provided, so the description carries the full burden. It only states the core action ('add a tag') with no additional behavioral details such as whether the operation is idempotent, what happens if the tag already exists, or whether permissions are required. The description is not misleading but is minimal.

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 clear sentence with no extraneous information. It is appropriately concise for a simple tool with two parameters.

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?

The tool is simple, has full schema coverage, and includes an output schema, reducing the burden on the description. However, the description does not address usage context or potential behavioral nuances. It is adequate for a basic add-tag operation but lacks any additional context that could help an agent decide when to use it.

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 description coverage is 100%: both 'contactId' and 'tag' have descriptions in the schema. The tool description adds little beyond the schema, merely restating the action and adding the 'Feather CRM' context. The schema already fully documents each parameter, so the baseline of 3 applies.

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 'Add a tag to a Feather CRM contact' clearly states the action (add), the object (tag), and the target (contact). It is specific and uses a verb-noun structure. However, it does not explicitly differentiate itself from the sibling tool 'add_label', which may perform a similar operation on labels rather than tags.

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. It does not mention any prerequisites, exclusions, or context where this tool is preferred. The sibling 'add_label' suggests a possible alternative for label operations, but no guidance is offered.

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