library

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

The description discloses 'newest first' as a sorting behavior but omits the fact that the 'limit' parameter (default 25) constrains the result set. This is a significant behavioral omission that could mislead an agent into thinking all stored items are returned when actually only a limited subset is.

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 description is one concise sentence that efficiently states the core action and ordering. Every word contributes meaning, and it is appropriately front-loaded.

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?

Even though the tool has only one optional parameter and an output schema exists, the description fails to mention the limiting behavior or provide any usage context. The agent cannot fully anticipate the output scope or how to request larger result sets.

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 schema defines 'limit' with a default but provides no description, and the tool description does not mention or explain this parameter. With 0% schema description coverage, the agent cannot accurately understand what 'limit' does or how it affects results.

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 uses a specific verb 'List' and identifies the resource as 'everything stored in the second brain,' with ordering 'newest first.' It clearly conveys a comprehensive listing action and implicitly distinguishes from more targeted sibling tools like 'recall' or 'remember.'

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?

The description provides no guidance on when to use this tool versus siblings like 'recall' or 'digest.' It lacks explicit alternatives, exclusions, or context for appropriate use, leaving the agent to infer when 'library' is the right choice.

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