furl_list

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

The description details the behavior: listing entries, ordering, pagination, and return fields. It does not mention any side effects, but the tool appears read-only. Given no annotations, it is sufficiently 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 concise with clear structure: purpose, return fields, pagination, alternatives. Every sentence adds value without 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?

It explains return fields and pagination comprehensively. No output schema exists, so the description compensates well. Minor gap: assumes knowledge of 'CCR entries' and 'session'.

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 descriptions for limit and offset. The description only mentions pagination generally, adding no new semantics 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 clearly states the tool lists stored CCR entries, newest first, and distinguishes it from siblings by mentioning alternatives: furl_retrieve for full original and furl_search for content search.

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 provides explicit guidance on when to use this tool (listing entries) and when to use alternatives (furl_retrieve, furl_search), covering typical usage scenarios.

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