todoist_activity_by_project

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

No annotations provided, so description must disclose behavior. It lists event types returned ('added/completed/deleted, comments, etc.') and states it returns activity log for a project. It does not disclose auth requirements, rate limits, or confirm it is a read-only operation. Moderate transparency.

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?

Two sentences with no redundancy: purpose, what it returns, and use case are all covered concisely. Front-loaded with the core action.

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 no output schema, the description provides examples of event types but does not explain pagination or return structure. Since the input schema covers pagination parameters, the description is mostly complete for a simple activity log tool.

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 each parameter has a description. The description does not add meaning beyond the schema; it merely summarizes that events are returned. Baseline 3 is appropriate since schema already provides parameter semantics.

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?

Description clearly states the verb 'Get' and resource 'Todoist activity log for a specific project', distinguishing it from siblings like todoist_activity_by_date_range which likely returns activity across projects. The purpose is specific and scoped.

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?

Description mentions tool is 'useful for project auditing and tracking project-specific changes', providing context for when to use. However, it does not explicitly contrast with alternatives or state when not to use, such as when date range filtering is enough via the by_date_range sibling.

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