smokeball_get_matter_items

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

With no annotations, the description carries the full burden. It only mentions routing and authentication scope (JWT, tenant, company), which is generic and likely applies to all tools. It does not disclose whether the tool is read-only, destructive, or requires specific permissions. The behavioral traits beyond the schema are almost entirely missing.

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, but it wastes space on routing details that are likely boilerplate. It does not front-load the key purpose or usage. For its minimal content, it is structurally acceptable but not efficient in conveying necessary information.

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?

The description is severely incomplete for an agent to use correctly. It does not explain the input arguments, the output semantics (despite having an output schema), or how this tool fits with siblings. The agent would need external knowledge of the Smokeball API to invoke it properly.

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 only as 'JSON string of arguments for the connector operation'. This adds no meaning beyond the schema's type and default. With 0% schema description coverage, the description must compensate by listing valid keys or providing examples, but it does not. The agent cannot infer what to include (e.g., matter_id, filters).

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 simply states the operation name 'get_matter_items' and the platform tool name, but does not explain what 'matter items' are or what the tool retrieves. It lacks a clear verb-resource pair (e.g., 'Retrieve items associated with a Smokeball matter'). Without domain knowledge, its purpose is ambiguous, and it does not distinguish itself from sibling tools like smokeball_get_matter or smokeball_list_matters.

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. There is no mention of when to prefer it over smokeball_get_matter, smokeball_list_matters, or other related tools. No prerequisites or context for invocation are given.

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