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

Annotations already declare readOnlyHint=true, idempotentHint=true, and non-destructive behavior, so the safety profile is covered. The description adds the ordering behavior ('oldest first') and the since-filtering semantics, which is useful but modest; it says nothing about result size, pagination limits, or retention.

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?

Three short sentences, front-loaded with what the tool returns, then usage, then the filter tip. No filler or repetition beyond conveying ordering.

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 list tool with full annotations and no output schema, the description covers what is returned and how to filter, which is enough to invoke correctly. Minor gaps remain: the verbs parameter is undocumented in prose and pagination via cursor is only implied.

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 75%, and since/cursor/project already carry schema descriptions. The description's 'Pass since to get only newer entries' largely restates the schema, and it is silent on the verbs enum, whose seven allowed values are the least self-explanatory part of the input. Baseline 3 is appropriate.

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 names a specific resource ('project activity') and enumerates the event kinds (milestones proposed/approved/completed/failed, goal changes), so the agent knows exactly what is returned. It does not explicitly contrast itself with siblings like get_updates or list_milestones, so it stops short of a 5.

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?

"Use it for 'what shipped' questions" gives one positive use case, which is helpful, but there is no guidance on when NOT to use it or which sibling (get_updates, list_milestones, get_project_status) to prefer for other questions. Usage is implied rather than delineated.

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