basecamp_create_campfire_line

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions the ability to include images/videos, but does not explain mutation consequences, permission requirements, or what happens on success/failure. This is minimal coverage for a create operation.

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 sentences with no redundancy. Every word adds value, stating the core purpose and a key capability in an efficient manner.

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 create tool, the description is adequate but sparse. It does not explain return values (no output schema) or provide any safety/permission caveats. Given the lack of annotations, a bit more context (e.g., 'This will immediately post the message to the chat') would improve completeness.

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 50%, with content and attachment_sgids described, but project_id and campfire_id left undefined. The description adds a hint that attachments can be images or videos, which partially compensates for the missing parameter context. However, it does not clarify the required IDs, so the added value is limited.

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 clearly states the tool's function with a specific verb ('Post') and resource ('a new message to a Campfire chat'). It is unambiguous and distinguishes from sibling tools like listing or deleting campfire lines.

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 implies a clear use case (posting to a Campfire), but does not explicitly state when to use it over alternatives or provide any exclusions. It lacks the explicit 'when/when-not' guidance seen in higher-quality descriptions.

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