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

The description discloses that the tool creates exactly one note, where it is stored (bound workspace or personal space), and instructs the agent to verbally confirm the location ('say it back'). These details go beyond the annotations, though non-idempotency is only weakly implied; the idempotentHint=false annotation covers that 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?

Four concise sentences, each carrying information: trigger phrases, creation/location behavior, title/body split, and the alternative tool. No filler or 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?

For a simple create tool with four documented parameters and no output schema, the description covers trigger, location, parameter intent, and alternative routing. Nothing critical is missing.

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 the baseline is 3; the description adds a useful division of labor between title and body ('Keep the title to one line... put the rest of the content in body') and reinforces the workspace/personal default from the scope enum. Labels are not expanded, but the schema already documents them.

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 opens with concrete trigger phrases ('save, write down, jot or note something') and names the exact resource: a new note on the member's Connections list. It explicitly contrasts with connections_todo_add, so an agent can distinguish it from siblings without ambiguity.

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?

It gives explicit when-to-use cue phrases and an explicit exclusion: 'Not for a task or reminder - use connections_todo_add for those.' It also clarifies the workspace-vs-personal placement rule, which is not obvious from the schema alone and prevents incorrect invocation.

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