Project activity

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

Annotations already declare readOnlyHint=true, and the description adds real value beyond that: it discloses the ordering (newest first), the return shape ({ at, type, ...details }), and the kinds of diagnostic content (failures with reasons). It does not mention pagination behavior for the limit cutoff, but is otherwise well-disclosed for a read-only tool.

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 dense sentences, front-loaded with the resource and ordering, followed by the return shape and a routing hint. Every clause carries information; no filler.

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 read-only, two-parameter tool with no output schema, the description supplies the return shape, ordering, event taxonomy, and sibling routing. Nothing essential to correct invocation is missing.

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 description coverage is 100%, so id and limit are already fully documented, giving a baseline of 3. The description adds only marginal meaning beyond the schema by implying chronological ordering; it does not elaborate on the limit's effect on older events.

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 and resource ('The project's pipeline history') and enumerates the exact event types returned (stage starts/completions, clip renders, retries, failures with reasons). It explicitly distinguishes itself from get_project, so an agent can separate the history tool from the current-state tool without inspecting schemas.

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?

Gives a concrete use case ('find out why something failed or is slow') and names the alternative (get_project shows current state). This is a clear when-to-use plus alternative, though it never states when NOT to reach for this tool or any prerequisites.

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