redmineflux_core_critical_issues

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

With no annotations, the description carries the transparency burden. It discloses key behavior: returns only urgent/immediate open issues, supports project filtering with empty meaning all projects, and caps results via limit. It does not mention ordering or pagination, which is a minor gap.

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 compact, front-loading the purpose, then giving a practical usage note, and finishing with concise argument explanations. It contains no filler or repetition.

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?

For a low-complexity tool with an output schema available and no annotations, the description is complete. It covers purpose, usage context, both parameters, and default behavior, making it easy for an agent to select and invoke the tool correctly.

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 fully explain parameters. It does: project_id is 'Filter to one project (empty = all projects)' and limit is 'Maximum issues (default 20).' This adds clear operational meaning beyond the raw schema.

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 opens with 'Get Urgent and Immediate priority open issues,' a specific verb-resource-scope combination. It clearly distinguishes this tool from the sibling list_issues by focusing on critical priorities and open issues.

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?

It explicitly says 'Use this during incidents, fire drills, or when someone asks...' and provides trigger phrases, giving strong contextual guidance. However, it does not explicitly mention when not to use it or point to an alternative for non-critical queries.

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