smokeball_list_layouts

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

Without any annotations, the description should disclose behavioral traits (e.g., read-only or destructive). It only mentions routing details (JWT, tenant, company scope), which are not behavioral. No insight into side effects or permissions.

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?

While technically concise, the description is under-specified. It wastes its few sentences on routing details rather than explaining the tool's core purpose, making it ineffective despite its brevity.

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 existence of an output schema, the description could be minimal, but it fails to explain what the tool actually lists (e.g., Smokeball document layouts). It leaves an AI agent without enough context to know when and why to invoke this tool.

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 a generic JSON string with no description in the schema or the tool description. The description just says 'JSON string of arguments for the connector operation,' adding no meaningful semantic beyond the schema's type and default value.

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 as 'Smokeball connector operation list_layouts' without specifying what layouts are or what listing them entails. It provides no concrete verb or resource, making it vague and tautological.

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 given on when to use this tool versus sibling tools like smokeball_get_layout, smokeball_create_layout, or smokeball_update_layout. It fails to differentiate its functionality.

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