Add Tag Instance To Project

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

Annotations already indicate write operation (readOnlyHint=false) and non-destructive mutation. The description adds value by detailing the successful response (HTTP 201, returns Tag Instance UUID) and the endpoint structure, which is beyond the annotations.

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 generally concise and front-loaded with the purpose and required parameters. However, it contains redundancy (mentions 'Resource Planning records' twice in different sentences) and could be slightly tighter without losing clarity.

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 creation tool with no output schema, the description fully covers the return value (UUID), success status (201), API resource path, and required parameters. No gaps are apparent given the tool's simplicity and the richness of the schema and annotations.

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?

Input schema covers all three parameters with full descriptions (100% coverage). The description merely repeats the required parameters without adding new semantic meaning, so a baseline score of 3 is appropriate.

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: 'make a Tag available to a Project' by sending a tag_id via POST. It specifies the return value (UUID) and distinguishes from siblings like 'add_tag_instance_to_person' and 'remove_tag_instance_from_project' by targeting project association.

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 creating Resource Planning records but does not explicitly state when to use this tool versus alternatives. No exclusions or when-not scenarios are provided; guidance is minimal beyond the core action.

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