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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the description goes further: it discloses the authorization-gated nature, that only orgs granting 'activities' rights appear, that it need not be joined, that non-interchange orgs are excluded, per-activity audience trimming, and pagination semantics (nextCursor passed through, changing alliance/filter restarts at page 1). This is substantial context beyond the structured hints.

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?

Front-loaded with the gating requirement, then behavior, then sibling routing in a compact multi-clause form. Dense but every sentence carries decision-relevant information; slightly long but no padding.

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?

With no output schema and 0% param coverage, the description supplies prerequisites, filtering semantics, exclusion rules, pagination behavior, and sibling routing. Near-complete; only the undocumented limit parameter and the cursor/nextCursor naming difference are loose ends.

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 0%, so the description carries the load. It explains organizationId (filters one authorized org), the category enum values (current/history/archived/pending) and the mixed-list default, and pagination via cursor/nextCursor. It omits limit (1-50, default 20) and does not map allianceId, leaving minor gaps at 5 params.

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 verb+resource (list alliance member organization activities) with precise scope: it aggregates activities from subordinate organizations that granted the 'activities' authorization, audience-trimmed at the service layer. It explicitly distinguishes itself from siblings list_organization_space_activities (alliance's own/featured) and get_signup_activity (signup details), so an agent can route without opening either 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 explicit prerequisites (login required, must hold alliance membership) and names the specific alternatives: list_organization_space_activities with the alliance organizationId for the alliance's own/featured activities, and get_signup_activity for signup details. It also states the alternative condition for organizationId (a single authorized org) and the default when category is omitted.

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