edit_conversation_note

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

No annotations exist, so the description must disclose all behavioral traits. It states the tool adds or replaces a note, but does not mention permissions needed, idempotency, side effects, or what happens if the conversation does not exist. This is minimal disclosure for a mutation tool with no 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?

Two sentences, front-loaded with the core action. No unnecessary words. Could be improved by listing identification methods more explicitly, but current structure is efficient.

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 9 parameters, no output schema, and no annotations, the description is too brief. It does not explain identification priority (e.g., what if multiple identifiers are given?), nor does it describe return values or error behavior. Sibling tools are not differentiated, leaving the agent guessing about appropriate use.

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 coverage is 100%, so baseline is 3. The description groups 'lead identifiers' but does not add new meaning beyond the schema's parameter descriptions (email, leadId, linkedinUrl). The grouping is mildly helpful but not substantial.

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 or replace a note') and the target resource ('inbox conversation'), with explicit identification methods (conversationId or lead identifiers). This distinguishes it from sibling tools that perform different functions like sending messages or listing conversations.

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 guidance on how to identify the conversation but does not give any when-to-use or when-not-to-use context. Siblings like 'send_linkedin_message' or 'get_conversation_messages' could be confused, but no exclusions or alternatives are mentioned.

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