redmine_create_issue

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

No annotations, so description must disclose behavior. Does not mention side effects, authorization needs, error conditions, or that it's a stable tool. Only says it creates and returns an issue.

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?

Concise (one sentence plus note) but lacks structure. No front-loading of key information beyond the basic purpose. Could be expanded without being verbose.

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?

With 12 parameters, no output schema, and no annotations, the description fails to provide necessary context. Does not explain field formats, required vs optional semantics, or system behavior. Very incomplete.

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% - description does not explain any of the 12 parameters. Does not add meaning beyond the schema itself, leaving the agent without guidance on usage.

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?

Clearly states verb 'create' and resource 'Redmine issue', and specifies that it returns the created issue with its ID. Distinguishes from sibling tools like redmine_update_issue, redmine_list_issues, etc.

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 on when to use this tool vs alternatives (e.g., redmine_update_issue) or prerequisites (e.g., project_id required). Only states what it does, not how to decide.

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