list_docs

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

Discloses ordering and default filters, but lacks details on pagination, rate limits, or what fields are returned, with no annotations to supplement.

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?

Single sentence is efficient and front-loaded, but could be slightly expanded without verbosity to cover key missing info.

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?

Incomplete for a 10-parameter tool with no schema descriptions; missing pagination, parameter explanations, and output schema context.

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?

Only mentions defaults for two parameters; the other eight parameters (query, workspace_id, etc.) are not explained despite zero schema description coverage.

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?

Clearly states it lists Coda docs accessible by the user with defaults and ordering, distinguishing it from sibling tools like create_doc or get_doc_info.

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?

Provides context on defaults but no explicit when-to-use or when-not-to-use guidance compared to alternatives like list_pages or list_tables.

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