Retrieve all todo lists in a Basecamp project by project ID. Use it to inspect a project's todo lists before managing tasks.
List all todo lists in a project
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | The project ID |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it only restates the listing action. It never states that this is a read-only operation, whether project access/permissions are required, whether results are paginated or truncated, or what happens if project_id does not exist.
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?
One short sentence, front-loaded with the verb and resource, with no filler or redundancy. Nothing could be removed without losing meaning.
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 single-parameter list tool, the definition covers the minimum: what it lists and its scope. Without annotations or an output schema it should at least note the read-only nature and return shape, which it omits.
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% and there is a single required parameter, so the schema already documents project_id fully. The phrase 'in a project' implies the scoping but adds no format, type, or validity detail beyond the schema.
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?
States a specific verb ('List') and resource ('todo lists') with scope ('in a project'), so an agent can distinguish it from get_todolist and create_todolist by intent. It stops short of naming a sibling explicitly, so it does not reach the 5 tier.
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?
No when-to-use guidance, no prerequisites, and no reference to the alternatives (get_todolist for a single list, create_todolist for creation). The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.