Project activity

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

With readOnlyHint already declaring safety, the description adds genuinely new behavioral context: live progress ticks are not stored (so polling will not surface in-flight state), the order is newest-first, and the return shape is given. It stops short of saying what a truncated result looks like or how far back history goes.

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 what the tool is and immediately followed by the qualifier about unstored ticks and the return shape. Every clause carries information, though the parenthetical and clause list make it slightly harder to scan than a purely linear phrasing.

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?

No output schema exists, but the description supplies the return shape and event taxonomy, which is the key missing piece. The only real gap is pagination/truncation semantics for limit, which matters for an agent that may need older events.

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 both id and limit are already fully documented in the schema, including the 1-200 range and default. The description adds only the ordering guarantee, not any meaning for the parameters themselves, so baseline 3 applies.

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 resource (the project's pipeline history) with a concrete scope and ordering (newest first), plus the exact event kinds returned. It explicitly contrasts with get_project's current-state view, so an agent can pick between them without opening a schema.

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 an explicit use case ("find out why something failed or is slow") and names the alternative (get_project) with the condition that selects it. It does not address the other overlapping siblings such as get_failure or get_queue, which also surface failure details, so the routing is clear but not exhaustive.

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