redmine_create_time_entry

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

Without annotations, the description fully carries the burden. It discloses several behavioral traits: hours are pre-validated client-side, spent_on defaults to today, comments max 1024 chars, user_id is admin-only override, project_id ignored when issue_id is non-zero, and it honors REDMINE_MCP_READ_ONLY.

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 well-structured with a one-line summary followed by a bulleted list of parameters. It is concise, front-loads the purpose, and every sentence adds value. No unnecessary words.

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?

Despite 0% schema coverage and no annotations, the description covers all 7 parameters, explains their behavior, and mentions the global read-only flag. With an output schema present, the lack of return value explanation is acceptable. The description is complete for agent use.

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?

With 0% schema description coverage, the description adds substantial meaning to each parameter: hours format and pre-validation, issue_id vs project_id logic, activity resolution, spent_on format and default, comments limit, and user_id role restriction. This goes well beyond the schema titles.

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 clearly states 'Log a time entry against an issue or project' using a specific verb and resource. It distinguishes itself from sibling tools like redmine_list_time_entries, redmine_update_time_entry, and redmine_delete_time_entry by focusing on creation.

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 implicitly tells when to use the tool (to log time) and provides parameter-level guidance (e.g., use issue_id or project_id). However, it does not explicitly contrast with alternative tools or state when not to use it, but the context is clear.

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