jira_label_add

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

Describes incremental addition (leaves other labels untouched), return format (YAML `{status: ok}`), and label constraint. Without annotations, this sufficiently discloses core behavior. Could mention error cases but acceptable.

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?

Three concise sentences. Each sentence adds unique value: core action, differentiation, return format. No redundancy or fluff.

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?

With no output schema and simple parameters, the description fully covers what the tool does, how to use it, and what to expect. Adequate for selection and invocation.

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 descriptions already cover both parameters. The description adds contextual meaning: incremental behavior and comparison to `jira_edit`, enriching parameter understanding beyond the schema.

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?

Clearly states the verb 'Add' and resource 'labels to a JIRA issue'. Specifically distinguishes from sibling tool `jira_edit` by noting incremental behavior, ensuring no confusion with bulk label replacement.

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?

Explicitly contrasts with `jira_edit` for label operations, guiding when to use this tool. Mentions label formatting constraint (no spaces). Lacks explicit 'when not to use' but the sibling comparison is strong.

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