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

Annotations already declare the safe read-only, idempotent, non-destructive, closed-world profile, so the bar is lower. The description still adds useful traits: results are ordered newest first, entries are anonymised, and each carries a one-line summary and URL. It does not state any count cap or truncation behavior.

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 sentence, front-loaded with the verb and resource set, with the return shape and ordering packed into trailing clauses. No filler.

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 usefully sketches the return shape (summary + URL) and ordering. It omits any note on result limits, pagination, or expected volume, which is a minor gap for a simple enum-filtered listing tool.

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 the baseline is 3, but the description genuinely enriches the single enum parameter by explaining what each value selects rather than restating 'work, projects or notes'. That added meaning beats the schema's bare enum list.

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?

Names a specific verb (List) and enumerates the three resources it returns, mapping each enum value to its plain-language meaning (work = anonymised client case studies, projects = side projects, notes = technical notes). It implicitly contrasts with the singular get_item sibling, though it never names an alternative outright.

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 implied by the enum values themselves: call this to enumerate everything of one content type. There is no explicit statement of when to prefer this over search or get_item, and no exclusions or prerequisites are given.

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