list_assets

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

The description notes read-only behavior and lists returned fields (asset type, title, scope, creation date, file path). With no annotations, this provides adequate transparency, though it could mention idempotency or lack of side effects.

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?

Two sentences, front-loaded with core action and result, then usage context, then return details. Every sentence adds value with no redundancy.

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?

Given a simple list tool with one parameter and no output schema, the description covers purpose, usage, return values, and sorting order comprehensively.

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 already fully describes the limit parameter with details. The description adds 'sorted most-recent-first' which reinforces but does not significantly add 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 explicitly states it lists recent structured memory assets (pinned memories and distilled briefs) sorted by creation date, clearly distinguishing it from sibling tools by specifying the asset types and the action.

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 says to use when needing an inventory before creating a new brief to avoid duplicates, providing a clear context. However, it does not mention when not to use or name direct alternatives, which would make it a 5.

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