upsert_conversation_note

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Create/update' which implies mutation, but doesn't specify permissions needed, whether this overwrites existing notes or merges them, rate limits, error conditions, or what 'upsert' specifically means in this context. The description is too minimal for a mutation tool with zero annotation coverage.

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, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for the tool's apparent complexity and front-loads the core functionality.

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?

Given this is a mutation tool with 4 parameters, 0% schema coverage, no annotations, but with an output schema present, the description is minimally adequate. The output schema reduces the need to describe return values, but the description should still address behavioral aspects like how 'upsert' works, permissions, and parameter meanings. It meets the bare minimum but leaves significant gaps.

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?

With 0% schema description coverage for all 4 parameters, the description provides no additional parameter semantics. It mentions 'product scope conversation' which hints at 'product_slug' and 'conversation_id', but doesn't explain what these identifiers represent, what format 'note' should take, or when 'client_id' is needed. The description fails to compensate for the complete lack of schema documentation.

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 ('Create/update') and target resource ('a conversation note for a product scope conversation'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from sibling tools like 'update_conversation_notes' or 'modify_conversion_notes', leaving ambiguity about when to use this versus those alternatives.

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 like 'update_conversation_notes' or 'modify_conversion_notes'. There's no mention of prerequisites, context requirements, or exclusions. The agent must infer usage from the tool name and parameters alone.

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