smokeball_list_folders

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

With no annotations, the description must disclose behavioral traits. It only mentions routing through an endpoint under JWT/tenant/company scope, but fails to state that this is a read-only operation, whether it supports pagination, or what happens on empty results.

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 short but omits critical details. While it avoids verbosity, it is under-specified and fails to provide the necessary information an agent needs to invoke the tool correctly.

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 has one parameter as a JSON string and no annotations, the description should explain the expected JSON structure or provide examples. It does not, 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 schema has a single parameter 'arguments' (JSON string) with 0% description coverage. The description only says 'JSON string of arguments for the connector operation,' adding no meaning about expected keys, structure, or defaults beyond what the schema already shows.

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 merely restates the tool name ('list_folders' and 'platform tool smokeball.list_folders') without specifying what is being listed (e.g., folders in Smokeball) or how this differs from other list tools like smokeball_create_folder. It lacks a clear verb-resource-object statement.

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, fallback tools, or scenarios where list_folders is appropriate versus other smokeball list tools.

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