smokeball_list_activities

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

With no annotations, the description carries full burden but only provides routing and authentication scope (JWT, tenant, company). Does not disclose read-only nature, rate limits, pagination, or if it lists all activities without filtering.

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?

Extremely short but under-specified. The description fails to convey essential information, prioritizing brevity over utility.

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 list operation with output schema assumed but not described, the description lacks details on filtering, sorting, pagination, or result structure. The input is a black box, making the tool nearly unusable without external documentation.

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 has 1 parameter 'arguments' (string, default '{}') with 0% description coverage. Description says 'JSON string of arguments for the connector operation' but does not clarify what fields the JSON should contain, leaving the agent guessing.

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 only restates the tool name ('Smokeball connector operation list_activities') without explaining what activities are retrieved or any scope of the list. It adds no value beyond the name itself.

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?

No guidance on when to use this tool vs alternatives (e.g., clio_list_activities or other smokeball list tools). No mention of prerequisites, filtering, or context.

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