basecamp_list_projects

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

With no annotations, the description bears full responsibility for behavioral disclosure. It simply says 'List all Basecamp projects' without noting that 'all' actually defaults to active projects only, nor that passing 'active' is rejected. This is a notable gap in describing the tool's actual behavior, though part of it is captured in the schema parameter description.

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 with zero wasted words. It is maximally concise while still conveying the core action and target resource.

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?

The tool is simple with one optional parameter and no output schema. The schema thoroughly covers the status behavior, and the description's short length is acceptable for a list operation. However, it could have explicitly stated the default active filter to avoid initial confusion, so it's not a perfect 5.

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 100%: the only parameter 'status' has a detailed description explaining defaults, allowed values, and rejection of 'active'. The tool description adds no parameter information, so the baseline 3 is appropriate since the schema carries the burden.

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 Basecamp projects' uses a specific verb and resource, clearly distinguishing this tool from related siblings like basecamp_get_project (single project) and basecamp_find_project (search). The purpose is immediately clear and unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it lists active projects by default or how to list archived/trashed ones, nor does it compare with find_project or get_project. The only usage hint is in the input schema, not the description.

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