redmine_create_time_entry

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

With no annotations provided, the description carries the full burden and does so well: it discloses that the tool honors REDMINE_MCP_READ_ONLY, that hours are pre-validated client-side, that activity resolves against a cached enumeration, that spent_on defaults server-side to today, and that comments cap at 1024 chars. It omits error/failure behavior and whether the entry is reversible, so it is not exhaustive.

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 summary sentence is front-loaded and each Args line earns its place by adding a distinct constraint or format. It is slightly long relative to a single-sentence ideal, but the density is justified for a seven-parameter tool.

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?

All parameters are documented, environment-variable fallbacks and read-only mode are explained, and an output schema exists so return values need not be described. Nothing an agent needs to invoke this tool correctly is missing.

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 description must compensate and it does: all seven parameters are explained with accepted formats ("2.5" or "H:MM"), defaults, mutual-exclusion rules, and permission constraints. This is meaning well beyond anything the bare schema conveys.

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 opening line names a specific verb and resource ("Log a time entry") and scopes the target to an issue or project, so the agent knows exactly what operation this is. It does not explicitly differentiate itself from the close siblings redmine_bulk_create_time_entries or redmine_update_time_entry, which keeps it from a 5.

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?

The description gives concrete selection conditions: either issue_id or project_id is required unless REDMINE_MCP_DEFAULT_TIME_ISSUE is set, project_id is ignored when issue_id is non-zero, and user_id is admin-only. It stops short of routing the agent away from sibling tools such as bulk_create_time_entries when logging many entries.

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