missive_update_shared_labels

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

Annotations declare the tool idempotent and non-destructive. The description adds context by explaining the partial update behavior ('only the attributes you include are changed'), which aligns with the annotations and provides additional clarity.

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 two sentences long, front-loaded with the action, and every word provides value without 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?

The description covers input well but does not mention the output or return value. For an update tool, knowing what is returned (e.g., updated labels or a success indicator) would improve completeness.

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?

The description elaborates on the single parameter 'shared_labels', clarifying the requirement for an 'id' and the optional nature of other fields. This adds meaning beyond the schema, which only specifies structure.

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 verb 'Updates' and the resource 'existing shared labels', distinguishing it from create operations. It specifies the action precisely.

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 explains how to provide objects with 'id' and that only included attributes are changed, indicating partial update behavior. It implies when to use but lacks explicit when-not-to-use or alternatives.

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