List Redmine trackers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: no pagination controls, field name mapping (id→id, name→name, etc.), version-dependent availability of description and enabledStandardFields, absence of browser links due to no show route, and error behavior (HTTP 401/403/404 without upstream body). It also explicitly states 'This tool never changes Redmine data,' reinforcing the read-only nature beyond the annotations.

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 dense but every sentence adds information: endpoint, auth, lack of controls, field mapping, version notes, link absence, error behavior, and safety guarantee. It is front-loaded with the core action and endpoint. Slightly long but justified given the version-dependent field details and error behavior; no filler.

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?

The tool has zero parameters, an output schema exists, and annotations cover safety. The description covers endpoint, auth, field mapping, version caveats, error behavior, and the absence of pagination/links. For a simple list tool, nothing an agent needs to call it correctly is missing. The output schema handles return values, so the description needn't repeat them.

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, and the schema is empty with 100% coverage. The description explains that there are no query, include, or pagination controls, which is meaningful context for an agent that might otherwise expect parameters. Since there are no parameters to document, the description's clarification that no controls exist is valuable and earns above the baseline.

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 reads all Redmine trackers from a specific endpoint (GET /trackers.json) for the configured API user. It distinguishes itself from sibling tools by naming the resource (trackers) and the read-only nature, and the title reinforces the resource. The verb 'Read' is specific and the scope is unambiguous.

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 explains that this endpoint accepts ordinary API authentication and has no query/include/pagination controls, which tells the agent when this tool is appropriate (simple list retrieval) and that no filtering is possible. It doesn't explicitly name alternatives, but the sibling list (e.g., list_projects, list_issue_statuses) makes the resource-specific usage clear. It also notes the HTML index is admin-or-API-only, implying this API path is the accessible route.

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