smokeball_list_tasks

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

No annotations exist, so the description must disclose behavioral traits. It notes routing through an API with JWT, tenant, and company scope, which is helpful for auth context. However, it omits critical details like pagination, read-only nature, rate limits, or response format. For a list operation, this is insufficient.

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 concise (two sentences plus routing info), but the brevity sacrifices utility. While it is front-loaded with the operation name, it lacks structure and the sentences contribute little information. It is minimally acceptable but not efficient in conveying value.

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?

Given the tool's simplicity and the presence of an output schema (which likely describes return fields), the description should provide context on what tasks are listed, typical use cases, or filtering. It fails to do so, leaving the agent without enough context to use the tool effectively.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation,' which adds no meaning beyond the schema. With 0% schema coverage, the description should compensate but does not; it offers no examples, required keys, or allowed values.

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 lists tasks from Smokeball via the 'list_tasks' operation. The name and text indicate the resource and action, which distinguishes it from sibling tools like clio_list_tasks and xero_list_tasks. However, it does not specify the nature of the tasks (e.g., matter-related or system tasks), leaving some ambiguity.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, filtering capabilities, or scenarios where this tool is appropriate or not. The description only gives technical routing details.

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