smokeball_list_matters

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

The description lacks any behavioral details beyond routing and arguments. With no annotations, it should disclose whether the tool is read-only, pagination behavior, rate limits, or side effects. None of this is provided.

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 relatively short but includes boilerplate about routing that may be unnecessary. It could be more concise and front-loaded with the core purpose.

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 complexity (a connector tool with a generic string parameter) and absence of annotations, the description is incomplete. It does not explain how to construct the arguments JSON, what fields are available, or what the output contains (though output schema exists).

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 parameter 'arguments' is described as a JSON string for the connector operation, which adds minimal value beyond the schema. With 0% schema description coverage, the tool would benefit from detailing possible keys (e.g., filters, sorting). No such detail is given.

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 only mentions 'Smokeball connector operation list_matters' and its routing, but never explicitly states that the tool lists matters. The purpose is implied by the name, but the description itself is vague and fails to clarify what the tool does beyond being a connector operation.

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 like smokeball_list_contacts or smokeball_list_files. There is no mention of context, prerequisites, or exclusions.

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