basecamp_get_todolist

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the purpose and does not mention any side effects, required permissions, return format, or error behavior. For a read-only operation, this is a minimal disclosure but lacks context that could help the agent anticipate behavior.

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 that states exactly what the tool does. No unnecessary words or repetitive content. It is clear and efficient.

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 get-style tool with schema fully covering parameters, the description is adequate but not rich. It does not explain what 'details' means or what is returned, but given the absence of an output schema and the simplicity of the operation, it is minimally complete. However, it could benefit from noting that it returns the full todolist object.

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%, so the baseline is 3. The parameter descriptions in the schema ('Project ID', 'To-do List ID') are minimal and essentially restate the parameter names, adding little semantic depth. The tool description does not add any parameter-level meaning beyond what the schema provides.

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 'Get' with a clear resource 'details of a specific to-do list'. The word 'specific' distinguishes it from list-like siblings such as 'list_todolists' and indicates a single-item retrieval by ID.

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 guidance is provided about when to use this tool versus alternatives. It does not mention that this should be used when you have a todolist ID, or that list_todolists should be used for browsing. Sibling tools exist but no differentiation is stated.

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