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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds the useful detail that results include size and that omitting path widens scope to the whole brain, but says nothing about ordering, pagination, or result limits for a potentially large listing.

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 terse sentence with the scope condition front-loaded after the resource. Nothing is wasted, though the fragment style omits a verb and reads more like a label than an instruction.

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?

With no output schema, the description is the only source of return-value information and does provide '(with size)'. For a listing tool that can span an entire brain, the absence of any note about result volume, ordering, or truncation leaves a meaningful gap.

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 documented in the schema but path has no description. The description compensates by defining path semantics ('under a folder' / omit for whole brain), which is exactly the missing piece, so it adds real meaning beyond the schema.

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 the resource clearly: notes and attachments under a folder, with a scope modifier (omit path for the whole brain). It is distinguishable from find_notes/search/files_by_tag by naming the listing scope, though it never uses an explicit verb and leans on the tool name to imply 'list'.

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 one conditional usage rule ('omit path for the whole brain'), which is genuinely useful. However, it never says when to prefer this over sibling enumeration/search tools such as find_notes, files_by_tag, or list_units, so the guidance is partial rather than comparative.

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