redmine_news_list

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

With no annotations, the description must carry the full burden. It only states the action and endpoint, but does not disclose pagination behavior, that it returns a list, or any read-only implications. No side effects or constraints are mentioned.

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 extremely concise with a single sentence and no wasted words. It front-loads the primary purpose. However, it is so sparse that it borders on under-specification rather than effective conciseness.

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 tool with 4 optional parameters and no output schema, the description is incomplete. It does not explain how parameters interact (e.g., fetch_all vs limit/offset), what the response structure looks like, or any filtering capabilities. The agent lacks essential information for correct invocation.

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 description coverage is only 25% (only project_id has a description). The description itself says nothing about parameters, so it does not compensate for the low coverage. An agent cannot understand the meaning of limit, offset, fetch_all, or project_id beyond their raw schema definitions.

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 news' clearly states the action (list) and resource (news), and the API endpoint adds specificity. It distinguishes from sibling tools like redmine_news_get, redmine_news_create, etc., by clearly indicating the list operation.

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 provides no guidance on when to use this tool versus alternatives like redmine_news_get. It does not mention pagination, filtering by project, or any conditions that would select this tool over others.

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