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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and mutation behavior are covered. The description adds useful context about current-user scope, newest-first ordering, and pagination, but does not describe return shape, total counts, or filter behavior beyond pagination.

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 a single front-loaded sentence with no filler. Every clause earns its place by stating resource, scope, ordering, and pagination support.

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 five optional filters and no output schema, the description is adequate but incomplete. It omits that the tool supports filtering by activity type, title text, and published state, and it gives no sense of the returned activity representation.

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 all five parameters are already documented in the schema. The description only explicitly mentions pagination and does not add syntax, defaults, or semantics for type, query, or published beyond what the schema provides.

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 gives a specific verb and resource: 'List the activities of the current user.' This clearly distinguishes it from siblings like create_activity or get_activity, but it does not explicitly differentiate it from list_my_media or describe how it differs from activity-search-related siblings.

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 states scope and ordering but gives no when-to-use guidance, no alternatives, and no exclusions. It does not tell the agent when to use this tool versus get_activity for a single record or how filtering should be approached.

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