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

Annotations already declare readOnly/openWorld/idempotent/non-destructive. The description adds real context beyond them: login is required, a pickActivities capability is needed, the service layer filters out the caller's own organization and ended activities, and pagination uses nextCursor.

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?

A single compact paragraph, front-loaded with the login and capability requirements, followed by filtering behavior and workflow. Every sentence carries information, with no redundancy.

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?

Covers prerequisites, filtering, workflow and pagination, which is good for a read-only list tool whose annotations cover the safety profile and which has no output schema. However, with 0% schema coverage, the unexplained query/limit/organizationId parameters leave a meaningful gap.

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% across four parameters (q, limit, cursor, organizationId), so the description must compensate but does not. Only 'cursor' is indirectly referenced via the nextCursor pagination note; q, limit, and organizationId semantics are unexplained.

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: searching publicly published activities that are pickable into the organization's curated space, and notes the service layer excludes own-org and ended activities. This distinguishes it from sibling listers like list_organization_activities and list_organization_space_activities, though it does not name them directly.

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 an explicit prerequisite ('requires pickActivities capability') and a workflow ('first view picked and signup cards, then confirm selection into organization space'). It provides clear context but does not explicitly name alternative tools or when-not-to-use conditions.

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