redmine_activity_feed

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

With no annotations, the description carries the full burden and largely succeeds: it discloses that the feed is synthesized across REST endpoints, merged by timestamp, and that a single failed source never fails the feed (errors surface per-source in 'sources'). It does not mention auth requirements, rate limits, or whether 'truncated' implies pagination continuation.

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?

Front-loads the one-line purpose and the design rationale before diving into Args and Returns. It is on the longer side, but given 0% schema coverage and a complex aggregation behavior, nearly every sentence earns its place.

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?

Complete for a complex aggregation tool: it explains what is returned (project, bounds, count, truncated, events, sources), documents the event shape, and covers the partial-failure edge case. An output schema also exists, so return-value explanation is a bonus rather than a gap.

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 compensate, and it does for every parameter: project (id or slug), from_date/to_date inclusive YYYY-MM-DD, activity_types subset with empty=all and list-or-CSV acceptance, limit 1-500, and max_per_source as the pre-merge per-source row cap. This adds real meaning far beyond the bare 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?

States a specific verb+resource: it 'synthesizes the feed' from per-resource REST endpoints and 'merges the events by timestamp' for recent project activity across issues, news, wiki, forums, time and files. This is clearly distinguishable from the per-resource siblings like redmine_list_news or redmine_list_time_entries because it produces a merged cross-resource timeline.

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?

Explains a strong usage rationale: Redmine's native /projects/:id/activity endpoint is not API-usable, so this tool exists to provide that aggregate view. However, it does not explicitly contrast when to prefer this merged feed over the individual per-resource list tools, leaving that routing decision to inference.

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