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

Annotations already declare readOnlyHint=true, and the description adds real context beyond that: audience boundaries (public/member/invited) are preserved, and a co-host relationship does not confer activity-management rights or access to private registration data. That permission scoping is exactly the kind of disclosure an agent needs when deciding whether this tool can answer a data question.

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 sentence with the scope front-loaded and no filler. The audience-boundary clause is slightly compressed and abstract, but every clause carries information.

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?

The read-only annotation and the permission-boundary sentence cover the safety profile, and no output schema exists so return values need not be explained. However, for a paginated, filterable list tool with zero schema documentation, the absence of any mention of filtering or pagination behavior leaves a real 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, so the description must carry the load and it does not. It implies an organization identity (mapping loosely to the required organizationId) but says nothing about the search term q, the limit default/cap, or cursor-based pagination, leaving three of four parameters unexplained anywhere.

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 states a specific resource and scope: visible activities where this organization is the host or co-host. That is enough to distinguish it from siblings like list_my_activities or list_alliance_member_activities, though it never names those alternatives explicitly and never uses a list verb outright.

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?

Usage is only implied: an agent can infer it should call this when it wants the activities tied to a given organization's host/co-host role. There is no explicit when-to-use versus list_organization_activities, list_activities, or list_organization_space_activities, and no stated prerequisites.

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