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

With no annotations, the description carries the full burden, and it does disclose two real traits: the operation is a read (non-destructive) and the return is plain text rather than rich formatting. It omits what happens when the id does not exist or the caller lacks access to the referenced workspace, and gives no sense of note size or truncation.

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?

One short sentence, no filler, and the plain-text return format is front-loaded alongside the core action. It is efficiently sized; the remaining gaps are omissions the other dimensions penalize rather than verbosity here.

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?

A two-parameter retrieval tool with no annotations and no output schema needs the description to compensate for the undocumented id parameter and to explain error behavior and workspace scoping. The description only covers the action and output medium, leaving an agent to guess at id format and failure modes.

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 50%: the workspace parameter is well-documented in the schema, but id is a bare string with no description anywhere. The description says nothing about either parameter — not the id format, not whether workspace must match the workspace the note was found in.

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 with scope: 'Read one Caddie note in full (as plain text)'. An agent can tell it retrieves a single note by id rather than listing or searching. It does not explicitly name siblings like search_notes or get_transcript, so sibling differentiation is only implied.

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?

There is no when-to-use guidance, no mention of search_notes as the way to obtain an id first, and no condition under which this tool should be preferred over search_notes or get_transcript. 'One ... in full' hints at single-item retrieval, but that is inference rather than stated guidance.

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