Create Basecamp Todo

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral traits beyond the basic 'create' action. It omits details about side effects, idempotency (though annotations set this false), permissions, or response behavior, which are important for a creation tool.

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 starts with its purpose but then includes a lengthy 7-bullet list of HTML formatting rules. While detailed, this makes the description longer than necessary; some rules could be summarized to improve conciseness without losing core information.

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?

Given the tool has 5 parameters (3 required) and no output schema, the description fails to explain what the function returns or confirm creation outcome. It also does not clarify the roles of bucket_id or todolist_id beyond the schema, leaving gaps for an agent to safely use the tool.

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 40%, with bucket_id and assignee_ids having minimal descriptions. The description does not clarify the missing parameter meanings (todolist_id, title, content) and instead provides extensive HTML formatting rules for the content parameter, which, while useful, does not substitute for parameter documentation.

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 states 'Create a new todo item in a todo list.' This clearly identifies the action (create), the resource (todo item), and the context (todo list), effectively distinguishing it from sibling tools like basecamp_complete_todo or basecamp_create_document.

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, such as when to create a todo versus a message or task. It lacks explicit context or exclusions, leaving the agent without decision-making support.

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