redmine_list_projects

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

Discloses pagination behavior, client-side filtering, and return format. With no annotations, the description covers the key behavioral aspects. Could mention any authentication requirements, but not critical for a read-only list tool.

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?

Structured with a summary line, Args section, and Returns section. Every sentence is informative and there is no redundant information. Front-loaded with the core purpose.

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 description covers the input parameters, behavior, and output format thoroughly. Given the tool's simplicity and the presence of an output schema (as implied by the description), the description is complete.

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?

All three parameters (query, limit, offset) are fully explained with behavior (client-side filter, max page size 100, defaults). Schema has 0% coverage, so the description carries the full burden and does so excellently.

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 'List projects' with key features: paginated, optional substring filter. It distinguishes from sibling tools like 'redmine_describe_project' and 'redmine_search' by being the specific listing tool for projects.

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?

Provides clear context on parameters and client-side filtering, but does not explicitly mention when to prefer this tool over alternatives like 'redmine_search' or other list tools. However, the filtering behavior is well explained.

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