list_projects

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

Beyond the readOnlyHint annotation, the description adds the behavioral qualifier 'active', indicating that archived or inactive projects are filtered out. It also names the specific API version (Basecamp Classic). While it doesn't detail pagination or response format, the output schema covers that, and the description adds useful context.

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: 'List all active Basecamp Classic projects.' Every word is meaningful, and there is no redundancy or unnecessary elaboration.

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 zero-parameter, read-only list tool with an output schema, the description is complete. It states what the tool returns (all active projects) and the domain (Basecamp Classic). The output schema handles return value details, and annotations handle safety. No additional context is needed.

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 tool has zero parameters, so the baseline is 4. The description adds no parameter-specific details, which is appropriate since there are none to describe. It contributes clarity about the fixed scope of the operation.

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 specifies the exact action (List), resource (projects), and scope (all active Basecamp Classic projects). This clearly distinguishes it from sibling tools like get_project, which retrieves a single project, and list_todo_lists, which targets a different resource.

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 implies when to use the tool (when you need all active projects), but it does not explicitly mention alternatives or exclusion criteria. For example, it does not say 'use get_project for a single project' or note that archived projects are excluded. The context is sufficient for a simple list tool, but no explicit guidance is provided.

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