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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that the underlying call is a POST to activity/list (a read masquerading as a POST, worth knowing) and that the batch is capped at 50, but says nothing about what happens with unknown ids or what comes back.

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 terse clauses with zero filler; the resource and the batch bound are front-loaded. The trailing 'POST activity/list' is jargon but informative to an API-aware agent.

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?

There is no output schema, so the description should indicate the return shape (activity records, ordering, behavior for missing ids) and does not. It is adequate to invoke correctly but leaves the agent guessing about the response.

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%, but the single parameter is a plain integer array whose constraints (minItems 1, maxItems 50) are already encoded in the schema. The description's only added semantics is where ids originate (policy or individual records), which is useful but thin.

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 the resource and the retrieval key precisely: activities fetched by id, in batches of 1-50. The 'by id' phrasing implicitly separates it from the sibling list_activities, though no verb ('get/retrieve') is used explicitly.

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 clause 'e.g. the ids shown on a policy or individual' tells the agent where valid ids come from, which is genuinely useful context. However, it never says when to pick this over agencybloc_list_activities or agencybloc_search_* alternatives.

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