superops_tickets_add_note

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

With no annotations, the description carries the burden of disclosing behavioral traits. It states 'Add a note' which implies a mutating operation, but it does not disclose potential side effects, permissions, or whether the note is appended to existing notes. For a simple note addition, this is adequate but not rich; more explicit disclosure of mutation safety or prerequisites would improve it.

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 filler. It communicates the primary action and a key parameter option ('internal or public') in a compact, front-loaded manner. Every word serves a purpose.

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 mutation tool with only 3 parameters and no output schema, the description covers the essential purpose and the main variation (visibility). It does not discuss response behavior or error handling, but given the simplicity and absence of an output schema, it is reasonably complete for an agent to call the tool correctly.

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 input schema provides full descriptions for all 3 parameters (100% coverage), so the schema already conveys their meaning. The description's mention of 'internal or public' adds a slight semantic layer to isPublic, but it largely repeats what the schema already states. This matches the baseline of 3 for full 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 ('add a note') and the target resource ('ticket'), and it distinguishes from sibling tools like create/update which operate on the ticket itself. However, it does not explicitly name any sibling or mention what it is not, so it lacks the explicit differentiation of a 5.

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 context that notes can be internal or public, which hints at the isPublic parameter usage. However, it does not explicitly compare against alternatives like send a message, log time, or custom_mutation, nor does it specify when to use this tool over others. The guidance is implied rather than explicit.

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