smokeball_api_request

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only mentions routing under JWT/tenant/company scope but does not disclose whether operations are read-only or destructive, error handling, rate limits, or success/failure behavior. This is insufficient for safe invocation.

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 brief (3 sentences) and front-loaded with the tool name and routing info. However, the first sentence redundantly restates the name. While not verbose, it could be more concise by removing redundancy and focusing on actionable details.

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?

Despite having an output schema, the description does not mention return values or structure. For a generic API request tool with no schema parameter descriptions, the description should provide comprehensive guidance on usage, available operations, and error handling, but it is lacking. It is incomplete for an agent to use 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 'JSON string of arguments for the connector operation,' which adds minimal meaning. With 0% schema description coverage, the description should detail expected JSON structure, but it does not. The parameter semantics are too vague for an agent to construct valid input.

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 states 'Smokeball connector operation api_request' but does not specify what operations are possible or how this tool differs from sibling tools like smokeball_request or specific actions (e.g., smokeball_create_matter). The term 'api_request' is vague and could refer to any API call, lacking a specific verb and resource.

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. With many specific Smokeball tools available (e.g., smokeball_create_matter, smokeball_list_matters) and a similar sibling 'smokeball_request', the description fails to clarify the appropriate context for using this generic request tool.

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