basecamp_list_campfires

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that it lists campfires visible to the current user, but it does not disclose whether the operation is read-only, the return format, ordering, pagination, or any side effects. For a simple list operation, some mention of return value or safety would improve transparency.

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, front-loaded sentence that gets straight to the point. It includes the essential clarifier '(group chats)' and the scope qualifier 'visible to the current user' without any filler or redundant 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?

The tool is simple with no input schema and no output schema. The description adequately conveys the core function and scope. It could be enhanced by stating the return type (e.g., 'returns a list of campfire objects'), but given the low complexity and lack of annotations, the description is nearly complete as is.

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?

The tool has zero parameters, so the description cannot add parameter-level meaning. Per the rubric, a baseline of 4 is given for tools with no parameters, and the description appropriately stays concise without attempting to document nonexistent parameters.

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 action ('List') and the resource ('all Campfires'), and includes a parenthetical explanation that defines the term. It also qualifies the scope with 'visible to the current user', distinguishing this from similarly named tools like 'basecamp_list_campfire_lines' which lists lines within a campfire, and 'basecamp_get_campfire' which fetches a single campfire.

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 the tool is used when you need to enumerate campfires for the current user, but it doesn't explicitly mention when not to use it or point to alternatives such as 'basecamp_get_campfire' for a single campfire. The context is clear but not fully elaborated with exclusions or alternative tools.

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