timeiq_report_recent_activity

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states the basic function — generating a feed — without explaining side effects, authorization needs, rate limits, or how the feed is returned (e.g., pagination, ordering). The description lacks critical operational context.

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 sentence of 12 words, which is extremely concise. While brevity is valued, it comes at the expense of necessary detail. The description is not front-loaded with the most critical information; it is merely a minimal summary. It could be restructured to include key constraints upfront.

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 complexity (7 parameters, no output schema, no annotations), the description is very incomplete. It does not specify output format (e.g., list of logs), date format requirements, whether parameters are exclusive or additive, or any default behavior. The agent would likely misinterpret how to invoke the tool correctly.

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?

With 0% schema description coverage, the description must add meaning to the parameters. It only mentions filtering 'by project or person', corresponding to the 'projects' and 'people' arrays. It does not explain 'start_date', 'end_date', 'clients', 'services', or 'extras', leaving the agent with insufficient guidance for proper usage.

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 generates a feed of recent activity/logs, with filtering by project or person. It distinguishes from sibling reporting tools (e.g., timeiq_report_time, timeiq_report_expenses) by focusing on a 'feed' of recent activity, which is unique among the many report variants.

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. It does not mention when not to use it, what other tools might be more appropriate (e.g., for detailed time reports), or any prerequisites (e.g., required permissions). The intended use case is only vaguely implied.

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