smokeball_list_files

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

With no annotations, the description carries full burden. It only mentions routing and JWT scope, but fails to disclose behavioral traits like read-only nature, side effects, or data boundaries. The agent cannot infer safety or impact.

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 includes unnecessary routing details (e.g., '/api/tools/invoke') that do not aid selection. The sentences could be reordered or merged for better front-loading of intent.

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 description omits essential context like what files are listed (e.g., all files, per matter, per folder), pagination, or output format. Despite having an output schema, the description does not help the agent understand the tool's scope or return shape.

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 coverage is 0% and the description only says 'JSON string of arguments for the connector operation.' This adds negligible meaning. The agent cannot determine what fields or format are expected for the arguments parameter.

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 identifies the tool as 'list_files' with a clear verb and resource. However, it does not differentiate from sibling list tools (e.g., smokeball_list_contacts, smokeball_list_matters), missing the opportunity to specify scope or context.

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 versus alternatives. The description lacks any conditional logic, prerequisites, or exclusions. An agent has no basis to decide between this and other smokeball list operations.

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