contacts_get_note

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds no extra behavioral context, such as return format or error conditions. It simply restates the action without value.

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 excessively terse at just 'Get Note', which is under-specification rather than effective conciseness. It lacks essential context and reads as a stub.

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 read operation with two required parameters, the description should at least mention what the response contains or how the note is identified. It provides none of that, and since there is no output schema, the burden falls on the description, which fails.

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 100% with brief descriptions for id and contactId. The tool description adds nothing about the parameters, so it relies entirely on the schema. Baseline 3 applies.

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 'Get Note' conveys a verb and resource but is minimal. It doesn't specify the domain (contacts) or that it retrieves a single note, leaving the agent to infer from the tool name and the contactId parameter. It is distinguishable from contacts_get_all_notes by the singular 'Note', but the description alone is vague.

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?

No guidance is given on when to use this tool versus alternatives like contacts_get_all_notes or contacts_get_task. The description provides no context, so an agent cannot determine the appropriate scenario.

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