basecamp_list_vaults

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'list' without clarifying whether it returns direct children only, whether it is read-only, or what the response format looks like. For a list operation, this leaves ambiguity about hierarchy depth and pagination.

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, front-loaded sentence that directly states the tool's purpose with no wasted words. It is concise and immediately informative.

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 the tool has two required parameters, no output schema, and many sibling tools, a bare one-line description is insufficient. It does not explain project_id, usage context, or what the response contains, leaving gaps for an AI agent to invoke it correctly.

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?

The input schema covers 50% of parameters (vault_id has a description) but project_id is undocumented. The description itself does not explain either parameter, so the agent lacks clarity on why project_id is required and how it relates to the vault.

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 a specific action ('List') on a specific resource ('all sub-vaults (folders) within a vault'). It also adds clarity by equating sub-vaults with folders, which distinguishes it from sibling tools like basecamp_get_vault or basecamp_create_vault.

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 usage is implied: to list sub-vaults, use this tool. However, there is no explicit guidance on when to prefer this over alternatives, no exclusions, and no mention of prerequisites like needing the correct project_id.

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