find-activity

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

Annotations already declare safe read-only behavior, so the bar is lower. The description adds valuable context: 'Shows events from all users by default' and 'Activity history availability and retention depend on the user plan.' These are behavioral traits not captured by annotations or schema.

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 four sentences, front-loaded with the core action, then layers filtering guidance and a caveat. Every sentence adds meaningful information, with no fluff or redundancy.

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 10-parameter tool, the description covers the main use cases, default behavior, example combinations, and plan-dependent retention. The output schema and parameter schema handle return values and pagination details, so the description is complete without over-explaining.

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 100%, so baseline is 3. The description adds meaning beyond the schema by explaining how to combine objectType, eventType, and dates for recurring completions, and by clarifying initiatorId as a user filter. This is a clear value-add over raw parameter descriptions.

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 opens with 'Retrieve activity logs to monitor and audit changes in Todoist,' a specific verb+resource combination. It clearly distinguishes itself from sibling find-* tools by focusing on activity logs, not entities. The additional examples (e.g., tracking task completions) reinforce the purpose.

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 gives concrete guidance: 'use objectType "task", eventType "completed", and dateFrom/dateTo' for completion queries, and notes initiatorId for user filtering. It does not explicitly mention when not to use it or contrast with alternatives like find-completed-tasks, but the context is clear enough for an agent to select it.

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