redmine_time_entries_list

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

With no annotations, the description carries the full burden of disclosing behavior. It does convey that this is a read-only listing operation via 'List' and the GET verb, but it says nothing about pagination defaults, fetch_all behavior, response format, or API limits. For a list endpoint, this is minimal but not wholly absent.

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 a single sentence and technically concise, but it is under-specified for a tool with 9 parameters and no other documentation. It is not that the words are wasted; it is that almost all necessary information is absent, making this more under-specification than effective conciseness.

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?

This is a list endpoint with a parameter-heavy schema, no annotations, and no output schema, yet the entire description is one sentence. An agent has no way to know about default limits, date input formats, available filters, or pagination behavior. The description is not remotely complete enough to support correct invocation.

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 schema has 9 parameters with 0% description coverage, and the description adds no parameter information whatsoever. Names like limit, offset, user_id, and project_id are self-evident, but date format for 'to' and 'from', semantics of 'fetch_all', and activity_id meaning are unexplained. The description completely fails to compensate for the lack of schema 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 states a specific verb and resource: 'List time entries (GET /time_entries.json).' This clearly identifies the operation and the API endpoint, and it distinguishes from CRUD siblings like redmine_time_entry_get or redmine_time_entry_delete by resource and action. However, it does not explicitly differentiate from other list tools beyond the resource name, which is implicit from the tool name.

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 tool versus alternatives, such as redmine_time_entry_get for a single entry or filtered list variants. No mention of use cases like date range reporting, user/project filtering, or pagination is provided. The agent is left to infer all usage decisions.

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