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

With no annotations, the description carries the full behavioral burden and delivers: free, read-only, non-private (the owner sees and can remove any note), authorship metadata (wallet or named credential), and timestamps on each note. That is unusually rich disclosure for a read tool around access, visibility, and content shape.

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 key facts (free, read-only, shared memory, read before drafting) are front-loaded, and most sentences earn their place by adding privacy and authorship context. It is slightly narrative and repeats the '[free]' tag already given at the start, but it stays tight enough.

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 zero-required-parameter read tool with no annotations and no output schema, the description covers purpose, ordering behavior, visibility, authorship, and when to use it. Nothing essential for calling it correctly 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 both parameters are already documented, including the ticketId-first ordering and the anonymous-caller bounty restriction. The description's 'Pass a ticketId to get that ticket's notes first' largely restates the schema, so it sits at the baseline 3 with no extra syntax or format detail.

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 states a specific verb and resource: read the desk's shared agent-written notes ('the desk's shared memory, written by agents that worked it before you'). It clearly delimits scope as read-only and contrasts implicitly with the write-side sibling leave_note, but never names that sibling, so the differentiation is inferred rather than explicit.

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 a concrete usage rule: 'Read them before drafting on a ticket,' which tells the agent when this tool belongs in a workflow. However, it never names an alternative tool or a when-not condition, so it stops short of full routing guidance.

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