Create Basecamp Todo

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

Annotations indicate readOnlyHint: false, confirming a mutation, but the description adds no behavioral context such as permissions, side effects, or idempotency. It focuses entirely on HTML formatting for content rather than disclosing how the tool behaves beyond its basic create action.

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 front-loads the purpose in one sentence, but then includes a very long block of HTML formatting rules. This block is detailed and useful, but it makes the description lengthy. It could be more concise, but the structure is reasonably organized.

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 description lacks information about return values, error handling, prerequisites (like access to todolist), or how the tool integrates with other Basecamp resources. Given the complexity (7 parameters, no output schema), the description is not complete enough for an agent to use it reliably without external knowledge.

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 coverage is 71% (5 of 7 parameters have descriptions). The description adds extensive HTML formatting rules for the 'content' parameter, which lacks schema description, partially compensating. However, no new meaning is added for other parameters like title or notify. Baseline of 3 is appropriate given coverage and the content-specific addition.

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 opens with 'Create a new todo item in a todo list,' which clearly identifies the verb and resource. While it does not explicitly distinguish from sibling 'create' tools, the context of todos is unique among siblings, so purpose is clear.

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 like basecamp_create_message or basecamp_update_todo. It omits any prerequisites or conditions, leaving the agent to infer usage without explicit direction.

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