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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by listing exactly what comes back (text, type, author, related contact and deal, created date) and pinning the underlying endpoint, which is useful since no output schema exists. It omits what happens on an unknown id, which keeps it from a 5.

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?

A single dense sentence plus the endpoint, with the returned-field list front-loaded before the path. No filler, though the sentence is a fragment rather than a complete statement of action.

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 one-parameter read tool with no output schema, the field enumeration compensates well for the missing return documentation and the annotations cover safety. The only shortfall is the absence of any error/not-found behavior for an id that does not exist.

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% and there is only one parameter, so the schema fully documents note_id including its pattern constraint. The description adds nothing about the id beyond the endpoint path, so the 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 identifies a single note or timeline entry retrieved by id and enumerates the returned fields (text, type, author, related contact/deal, created date), which makes the resource concrete. It does not explicitly state the verb 'retrieve', relying on 'by id' plus the endpoint path to convey that, and it does not name a sibling, so it stops short of a 5.

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?

Usage is only implied: 'by id' signals that the caller must have a note id in hand, and the alternative to reading is obviously revampcrm_add_note. There is no explicit when-to-use or when-not guidance, and no note that timeline entries are covered by the same call beyond the passing phrase 'or timeline entry'.

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