basecamp_create_message

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely states 'Post a new message' without explaining permission needs, return values, side effects, or prerequisites like pre-uploading attachments. This is insufficient for a create tool with minimal annotation support.

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 two short, front-loaded sentences with no redundant words. The first sentence states the core action and target, and the second adds a key capability. Every phrase earns its place.

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?

With no output schema and five parameters, the description lacks information about return format, prerequisites (e.g., project existence, attachment upload order), or potential side effects. It is adequate for a basic invocation but incomplete as a full tool contract.

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 60%, and the description adds meaning by explicitly stating that images and videos can be included (related to attachment_sgids) and that the message targets a message board. However, it does not clarify project_id or message_board_id beyond the names, so it only partially compensates for the schema gaps.

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 the specific verb 'Post' and clearly identifies the resource as 'message/announcement to the message board,' distinguishing it from sibling tools like basecamp_comment, basecamp_update_message, and basecamp_list_messages. It also mentions the capability to include images and videos, adding specificity.

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 this tool is for creating new messages on a specific message board, providing clear context. However, it does not explicitly state when not to use it or mention alternatives such as basecamp_comment for replies or basecamp_update_message for edits.

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