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

Annotations already declare non-readOnly, non-idempotent, destructive, closed-world, so the safety profile is largely covered. The description still adds real behavior: exactly ONE note is created, the destination is resolved to the bound workspace or personal space, and the reply names which (so the agent should echo it back). It does not explain why the call is flagged destructive or what happens to an existing note with a similar title, leaving a modest gap.

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?

Front-loads the trigger condition, then the creation semantics, then destination resolution, then the sibling exclusion - a sensible ordering. Slightly dense but nearly every clause carries instruction value; the 'so say it back' aside is short and actionable.

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 4-parameter mutation tool with no output schema, the description covers the trigger, the destination resolution, and the follow-up behavior (reply names the space), which is most of what an agent needs. The only unaddressed item is the destructiveHint=true flag, which the description neither explains nor contradicts.

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 description coverage is already 100%, so the baseline is 3. The description adds styling guidance beyond the schema by telling the agent to keep the title to one line naming the thing and to put the remaining content in `body`, plus it restates the scope default resolution in prose.

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?

States a specific verb and resource ('Creates ONE new note on the member's Connections list') and immediately contrasts with the sibling it is not: connections_todo_add for tasks and reminders. An agent can distinguish it from connections_notes_search and connections_todo_add without opening a schema.

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?

Gives explicit trigger phrases the member might use ('save this', 'make a note of that', 'write this down') and an explicit exclusion with a named alternative ('Not for a task or reminder - use connections_todo_add'). This is about as unambiguous as routing guidance gets.

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