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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive. The description adds the target entity types but does not disclose any additional behavioral traits such as whether the note is appended, returns an ID, or triggers side effects. It matches the annotations, so no contradiction, but adds minimal behavioral insight.

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 concise sentence, front-loaded with the verb, and contains no filler words. It efficiently communicates the action and target entities.

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 the simple nature of the tool, the description is nearly complete, but the 'member/account' vs. 'account' mismatch is a clear gap. It does not provide usage context or highlight the isPinned option, though the schema covers parameter details. The output schema exists, so return values are not needed.

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 schema covers 100% of parameters, so the baseline is 3. However, the description introduces 'member/account' while the entityType enum only includes 'account', 'booking', 'ticket', and 'invoice'. This discrepancy could mislead an agent into using an invalid entityType 'member'. The description adds no value beyond the schema and actually introduces confusion.

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 uses a specific verb 'Add' and identifies the resource ('a note') and the target entities (member/account, booking, ticket, or invoice). This clearly distinguishes it from sibling tools like create_post or create_task, which have different purposes. The scope is immediately understandable.

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 implies when to use the tool: whenever a note needs to be added to one of the listed entity types. However, there is no explicit when-to-use/not-to-use guidance or mention of alternatives, which would be helpful for less obvious cases. The lack of exclusions or context beyond the target list leaves some ambiguity.

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