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

Annotations already declare readOnly, idempotent, non-destructive, closed-world semantics, so the safety profile is covered. The description adds genuinely useful context beyond that: the entries are 'private' and 'durable', and the return shape is characterized via title/description/origin. It does not say whether results are complete or paginated, which matters for a list tool.

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 front-loaded sentence with a clean colon-delimited enumeration of what is returned. No boilerplate, no restatement of the tool name.

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 helpfully documents the return shape (title, generated description, origin enum). However, it is silent on the required websiteId and on result completeness/ordering, leaving gaps an agent would want before calling.

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?

The single required parameter websiteId has 0% schema description coverage, and the description only implies scoping via the possessive 'the website's' without ever mentioning the parameter, its meaning, or its format. With coverage this low the description is expected to compensate, and it does not.

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 ('Lists') and a precisely scoped resource ('the website's private durable context entries: uploaded files and pasted text'), with the entry shape spelled out. It never contrasts itself with sibling operations like websiteKnowledge_search or websiteKnowledge_read, so an agent must infer that this is the exhaustive list vs. the query/get variants.

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 explicit when-to-use guidance and no alternatives named, despite five closely related siblings (search, read, view, project_get, create). The 'List' verb implies enumeration, but nothing tells the agent to prefer search for filtering or read for full entry content.

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