List Basecamp Vaults

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

Annotations already indicate a safe, read-only operation. The description adds context about the location ('Docs & Files') and hierarchy, but does not disclose behavioral traits beyond what annotations convey (e.g., pagination, limits, ordering).

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 a single, concise sentence (14 words) that is front-loaded with the main action and context. Every word is necessary, 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?

For a simple list operation with clear annotations and schema, the description is sufficient. It could optionally mention that it returns an array of vault objects, but given the tool's nature and annotations, this is not a major 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?

Input schema covers all parameters with descriptions, so baseline is 3. The description does not add extra meaning beyond the schema; it only implies the use of parent_vault_id.

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 action ('List'), the resource ('sub-vaults (folders)'), and the context ('under a parent vault in the Docs & Files section'). It distinguishes from sibling list tools like basecamp_list_documents by specifying 'vaults' and 'folders'.

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 the tool is used when you have a parent vault ID and want to see sub-vaults, but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools or prerequisites.

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