smokeball_list_staff

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the description adds useful context: calls route only through the exact project/account governed connector authority, and Spring verifies the required `read` effect. It does not disclose operation-specific behavior such as pagination or response shape, and the `approval_ref` write-resumption note is irrelevant to a read-only tool.

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 compact, front-loads the operation identity and routing constraint, and uses a clean parameter-list format. The first line is somewhat redundant with the tool name, but no sentence is wasted.

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?

With an output schema and read-only annotations present, the description does not need to re-explain return values or safety. However, it is thin on Smokeball-specific meaning: it never states that the operation lists staff members, what arguments the operation accepts, or when to use it, leaving the agent to infer from the tool name alone.

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 description coverage is 0%, but the description compensates by explaining all seven parameters with meaningful one-line semantics: project_id, project_ref, connector_account_ref, idempotency_key, effect, and approval_ref. The main gap is that the contents of the `arguments` JSON string are left opaque, so the agent does not know operation-specific arguments beyond the default `{}`.

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 first line identifies a specific Smokeball operation, `list_staff`, and the schema's `effect: const read` confirms this is a read/list action. The tool name and description together communicate that this lists staff records, though the description never explicitly says what `list_staff` returns or distinguishes it from sibling Smokeball list tools.

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?

The description gives no guidance on when to choose this tool over alternatives such as smokeball_list_contacts, smokeball_list_matters, or smokeball_integrated_search. The routing and authority notes describe constraints, not selection criteria.

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