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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds useful scope (user's own chats) and returned fields, but says nothing about pagination behavior or ordering beyond the bare word "recent".

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 efficiently front-loaded sentence with no filler. The only waste is the "Jobs —" prefix, which costs tokens and briefly points toward the wrong domain.

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?

An output schema exists and annotations are rich, so the description need not explain return values. It is adequate for this simple two-parameter read tool, though a hint about ordering or what "recent" means would close the remaining gap.

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%, with limit and cursor fully documented (default 20, max 50, next_cursor semantics). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 and resource ("List the user's recent Worklittle chats") plus the fields returned (title and status) and the consumer (app sidebar). It cannot differentiate from a chat sibling because none exists, but the "Jobs —" prefix slightly muddies an otherwise clear purpose.

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 only implied by "for the app sidebar"; there is no explicit when-to-use, when-not-to-use, or alternative routing. "Recent" is never defined, leaving the agent to infer ordering and scope.

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