smokeball_list_time_entries

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 details and does not disclose read-only nature, authorization requirements, rate limits, or pagination behavior. The agent is left uninformed about important side effects or constraints.

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 includes unnecessary routing details (e.g., 'Routes through /api/tools/invoke ...') that distract from the core purpose. It could be more concise and front-loaded with the key action.

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 presence of an output schema, the description could reference it to explain return values, but it does not. The description lacks essential context about filtering, ordering, and expected results, leaving the agent underinformed for a simple list 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?

The single parameter 'arguments' is described generically as 'JSON string of arguments for the connector operation.' With 0% schema description coverage, the description should explain what specific arguments are expected for listing time entries, but it adds almost no meaningful information beyond the schema.

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 mostly restates the tool name ('Smokeball connector operation `list_time_entries`') and includes irrelevant routing details. It lacks a clear, standalone statement of what the tool does, making it close to a tautology.

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 or when not to use this tool. There is no comparison to sibling tools like `smokeball_create_time_entry` or other smokeball list operations, so the agent has no help in selecting the correct tool.

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