basecamp_list_campfire_lines

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 the action but does not disclose pagination, ordering, rate limits, permission requirements, or what data is included (e.g., whether attachments or system messages are included). Without any behavioral context, the agent cannot anticipate the tool's exact behavior beyond the obvious read 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 a single sentence, front-loaded with the primary verb and object. Every word earns its place, with no fluff or repetition. It is optimally concise for a simple list operation.

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 annotations, no output schema, and no parameter descriptions, the description is the only source of context. While the tool is simple, the description omits critical usage details such as parameter roles, return format, and any pagination or filtering behavior. Compared to similar tools with richer annotations, this leaves significant gaps for the agent.

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 0% and the description does not explain the parameters. The phrase 'in a Campfire' loosely relates to campfire_id, but project_id is left unexplained. The parameter names themselves are self-explanatory, but the description adds no additional meaning beyond the schema's property names, failing to compensate for the complete lack of schema descriptions.

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 ('List') and resource ('chat messages/lines in a Campfire'), clearly distinguishing this tool from siblings like basecamp_list_campfires (lists campfires) and basecamp_create_campfire_line (creates a line). It also clarifies the synonym 'lines' for chat messages.

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. It does not mention that this is the tool for retrieving Campfire chat history, nor does it exclude other list tools or suggest a preferred scenario. Usage is only implied by the name and basic action.

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