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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real value beyond that: 'nextCursor continues to older results' discloses pagination direction, and the project-access/public-sharing sentence discloses an authorization limitation that no annotation conveys.

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 tight sentences, front-loaded with what the tool returns and how to page through results, with the access caveat last. No filler, though the 'nextCursor' label doesn't match the actual 'cursor' parameter name, which is a small source of friction.

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 six-parameter tool with a nested cursor object and no output schema, the description covers purpose, pagination, and permission scoping but omits the response shape entirely and under-documents the parameter set. It is workable but leaves gaps an agent would have to discover by trial.

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 0%, so the description must carry the burden. It maps to roughly four of the six parameters (date range, actorId, completed, cursor pagination) but leaves projectId unaddressed, doesn't explain that the cursor is a structured at/id object, and gives no format hints for the date-times.

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?

Names a specific verb and resource ('Read authorized changes across projects') with a scope qualifier, so the agent knows this is an activity/audit feed. However, it never distinguishes itself from similar siblings such as get_history, get_tasks, or show_tasks, leaving the agent to guess which read tool applies.

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 filter list (dates, actor, completed tasks) implies the query contexts this tool fits, and the 'only current project access applies' sentence sets a scope boundary. But there is no explicit when-to-use guidance, no prerequisites, and no named alternative among the many read siblings.

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