basecamp_list_documents

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

No annotations are provided, so the description carries the full burden. It only states the operation, but does not disclose behavior such as whether the list includes archived/trashed documents, pagination, ordering, error cases, or what fields the returned documents contain.

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 entire description is a single short sentence, front-loaded with action and resource. No unnecessary words.

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 no output schema and no annotations, the description is underspecified. It fails to describe return values, pagination, or any behavioral caveats. While the tool is simple, the description leaves the agent guessing about what 'documents' means and what the response looks like.

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 only 50% (only vault_id has a description). The description adds minimal parameter insight—it mentions 'vault' but does not explain that project_id is a parent project or what relationships are required. It does not compensate for the undocumented project_id parameter.

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 'List all documents in a vault (Docs & Files)' uses a specific action ('List') and resource ('documents'), with clear scope ('in a vault') and a clarifying parenthetical. It clearly distinguishes this from get/create/update document tools by indicating it's a list operation.

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?

The description implies usage: if you need to list all documents in a vault, use this. However, it provides no explicit guidance on alternatives or exclusions, such as noting that get_document retrieves a single document or that uploads are handled separately.

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