smokeball_list_time_entries

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

Annotations already carry the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description is consistent with them — effect 'must be read' and 'Spring verifies it' reinforces the read-only contract. The governed-routing note adds a small amount of context, but there is no disclosure of pagination, result-set behavior, or data freshness beyond what annotations imply.

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 and well-organized: a title line, a single routing constraint, and a labeled Args block with one-line-per-parameter definitions. There is no filler; the only mild redundancy is the opening sentence, which largely repeats the tool name and platform path.

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 presence of an output schema covers return values and annotations cover safety, but an agent is still left unable to determine what arguments the list operation actually accepts, what Smokeball-specific semantics apply (e.g., matter scoping, billing-state filters), or when to prefer this over sibling list tools. The definition is generic connector plumbing that does not distinguish this tool's behavior from any other smokeball_* operation.

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%, so the Args block bears the full burden and does provide one-line definitions for all 7 parameters (project_id, project_ref, connector_account_ref, etc.), which is better than the bare schema. However, the semantically central parameter, arguments, is left as an opaque 'JSON string of arguments for the connector operation' with no Smokeball-specific filters or fields specified, so an agent still cannot construct a meaningful listing call.

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 leading sentence ('Smokeball connector operation list_time_entries') restates the tool name rather than explaining what listing time entries does, what it returns, or its scope. The name itself is genuinely informative (a read-only list of time entries in Smokeball), but the description never elaborates the functional purpose — the rest is connector-routing boilerplate that would fit any smokeball_* tool.

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 on when to choose this tool over alternatives such as smokeball_list_tasks, clio_list_time_entries, or xero_list_time_entries. The only directive, 'Routes only through the exact project/account governed connector authority,' is an execution constraint, not a selection criterion, and offers no when-to-use or when-not-to-use context.

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