redmine_log_time

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

With no annotations provided, the description must disclose behavioral traits, but it only states that the tool returns the created time entry. It does not mention side effects, failure modes, idempotency, authentication requirements, or rate limits. The behavior beyond creation is opaque.

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 extremely concise: two sentences that front-load the core purpose and a critical constraint. No extraneous information; every sentence earns its place.

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 tool's complexity (6 parameters, 2 required, no output schema, no annotations), the description is incomplete. It misses parameter meanings, allowed values (e.g., activity_id), behavior when both issue_id and project_id are provided, and the exact response format. A more detailed description would be needed for proper use without external knowledge.

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 coverage is 0%, so the description must compensate. It adds meaning for issue_id and project_id by clarifying that one is required, which is not enforced by the schema (both are optional). However, it does not explain other parameters like hours, comments, spent_on, or activity_id, leaving their semantics unclear.

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 the tool's purpose: 'Log time against a Redmine issue or project.' The verb 'log time' is specific and distinguishes this tool from siblings like redmine_get_time_entry (read) or redmine_update_time_entry (update). It also mentions returning the created entry, reinforcing that this is a create operation.

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 provides one constraint: 'Either issue_id or project_id is required.' However, it offers no guidance on when to use this tool versus related tools like redmine_update_time_entry or redmine_list_time_entries. No prerequisites, exclusions, or alternative selection criteria are mentioned.

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