basecamp_get_vault

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

No annotations are provided, so the description carries the burden. It communicates a read-only intent ('Get'), but does not disclose behaviors such as what details are returned, error handling, or permission requirements. Minimal but not misleading.

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 that is front-loaded with the key verb and object. It contains no redundant or filler words, earning a top score for brevity.

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 getter with two required parameters and no output schema, the description is mostly complete. It could have mentioned that the vault must belong to the specified project, but the core purpose is adequately conveyed without overloading the description.

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 description coverage is 0%, and the description adds no parameter-level context. Although the parameter names 'vault_id' and 'project_id' are self-explanatory, the description does not compensate for the lack of schema descriptions, leaving the agent to infer that both are needed to locate 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 the action ('Get details') and the target resource ('vault'), even clarifying that a vault is a folder. It also distinguishes from sibling 'list_vaults' by specifying 'a specific' vault, indicating a single-resource retrieval.

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 need details of one vault by ID, but does not explicitly state when to prefer it over list_vaults or other getters. No exclusions or prerequisites are mentioned, so usage is only implied.

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