List Basecamp Uploads

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description's safety profile is already known. The description adds the behavioral context that the operation is a list of uploads, which aligns with the annotations. No additional behavioral traits (e.g., pagination, rate limits) are disclosed, but none are necessary given the annotations.

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 10-word sentence that is front-loaded with the key action and resource. Every word is essential, with no redundancy or filler. It is perfectly concise for the tool's purpose.

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 that there is no output schema and the tool has only three parameters with nested objects, the description provides the fundamental context. It could be slightly improved by hinting at the return format (e.g., list of upload metadata), but it is largely sufficient for a read-only list tool with strong annotations.

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 provides full descriptions for all three parameters (100% coverage), so the baseline is 3. The description does not add any meaning beyond what the schema already provides. For example, it does not clarify how the filter parameter works beyond what the schema states ('regular expression').

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 uses a specific verb 'List' and clearly identifies the resource as 'files uploaded to a vault in the Docs & Files section.' This distinguishes it from sibling list tools like basecamp_list_documents and basecamp_list_vaults, which operate on different resources.

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 clearly states the tool lists uploads in a vault, which implies it should be used when the agent needs to retrieve uploads rather than documents or other content. While it does not explicitly state when not to use it, the context of sibling tools provides sufficient guidance.

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