list_areas

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It conveys that the tool exposes six canonical areas and implicitly suggests a read-only retrieval, but it never explicitly states that it returns a list, whether the data is static, or that there are no side effects. This is adequate for a simple zero-parameter tool but not richly transparent.

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 a single, efficient phrase with no filler. It front-loads the essential information and is appropriately sized for a zero-parameter read-only listing tool.

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 an output schema present and no parameters, the description largely suffices for a trivial list operation. However, it leaves the action implicit and provides no contextual guidance about when the six areas would matter or how they relate to sibling tools, making it minimally complete rather than fully self-contained.

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 tool has zero parameters and an empty input schema, so the baseline of 4 applies. No parameter documentation is needed, and the description does not mislead about any arguments.

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 identifies the resource clearly as 'the six canonical areas of the knowledge library,' which is specific enough to distinguish it from note- and project-related siblings. However, it lacks an explicit verb in the description itself; the action 'list' is only present in the tool name.

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 guidance on when to use this tool versus alternatives such as list_projects or list_permanent_notes. An agent must infer from the tool name and the word 'areas' when this is appropriate, since the description does not state any context, exclusions, or alternative routing.

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