redmine_list_trackers

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It merely states the action without mentioning return format, pagination, sorting, or whether all trackers (including inactive ones) are returned. For a simple list tool, the description is thin on behavioral context beyond the obvious read-only nature hinted by 'List'.

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 a single, front-loaded sentence with zero wasted words. It fully conveys the core action in a compact form, fitting the tool's simple nature.

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 simplicity (no parameters, no output schema), the description is minimally adequate but leaves gaps around return structure and any inherent filtering or scope. It does not explain what fields a tracker record contains or how the result might be consumed, which could require an agent to infer too much.

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?

The tool has zero parameters, so there is nothing to document. Per the scoring rule, a tool with 0 parameters receives a baseline of 4; the description adds no parameter information because none exists.

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 'List all available issue trackers' uses a specific verb ('List') and a clear resource ('issue trackers'), making its purpose immediately obvious. It naturally distinguishes itself from sibling tools like redmine_list_statuses and redmine_list_priorities by naming the specific resource.

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 does not explicitly state when to use this tool versus alternatives, but the clear resource name implies the use case. Since there are many list tools among siblings, explicit guidance (e.g., 'Use when you need tracker IDs for creating/updating issues') would improve clarity, but the intent is still reasonably inferable.

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