list_project_events

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

No annotations exist, so the description bears full responsibility. It explains the limit parameter behavior (most recent N events, 0 for all) but does not explicitly state the tool is read-only. The verb 'list' strongly implies non-destructive behavior, but a explicit safety note would be beneficial.

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: one sentence plus a brief docstring. Every sentence adds value with no redundancy or fluff.

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 presence of an output schema (not shown), the description does not need to detail return values. It covers purpose, parameters, and return type ('Dictionary containing the list of project events'). However, it does not specify ordering (e.g., most recent first) or pagination, which could be inferred from the limit parameter but is not explicit.

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?

The schema has 0% description coverage, but the description's docstring explains both parameters: project_id as 'ID of the project' and limit as 'Return only the most recent N events; 0 returns all events.' This adds meaning beyond the bare schema titles and types.

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 'List events related to a project.' This is a specific verb-resource pair that distinguishes it from sibling tools like 'list_events' (broader) and 'get_last_events' (more focused).

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 implies usage for listing events filtered by project but does not explicitly contrast with siblings or state when not to use it. No usage restrictions or alternatives are mentioned.

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