legal_smokeball_matter_operations

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

Annotations already mark this as destructiveHint=true and readOnlyHint=false, so the description should clarify side effects, but it does not warn about destructive behavior or explain what may change. It only adds routing/scope context (JWT, tenant, company), which is useful but far from sufficient for a potentially destructive generic action runner.

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, front-loaded with the primary command, and uses a clean Args layout. The routing sentence is relevant context, though it could have been used to explain behavior instead. There is no padding or redundant restatement beyond the name in the first sentence.

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 the presence of an output schema, the core action is undefined: an agent cannot tell what matter operations are possible, what a valid message or inputs payload looks like, or when this generic dispatcher should be chosen over dozens of directly named sibling tools. For a destructive, non-idempotent action runner, this is a significant completeness gap.

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%, and the description's Args block does add some meaning: message is a free-text objective and inputs is an optional JSON string for structured inputs. However, it does not provide valid keys, expected shapes, examples, or how these relate to specific matter operations, so it only partially compensates for the schema's lack of documentation.

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 says 'Run the legal domain agent action smokeball_matter_operations', which is essentially a restatement of the tool name. It adds that the call routes through a domain-agent dispatcher, but never explains what 'matter operations' actually does, what kinds of operations it supports, or what it produces. An agent cannot distinguish this wrapper from the many direct smokeball_* matter tools or other legal_* domain actions.

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?

There is no guidance on when to use this dispatcher-style tool instead of alternatives like smokeball_create_matter, smokeball_update_matter, legal_smokeball_orchestration, or the broader legal_domain_agent family. The description mentions routing and scope but gives no conditions, prerequisites, or exclusions.

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