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

Beyond the readOnlyHint annotation it discloses substantive behavior: audience-based visibility relaxation for members, that invited userIds are withheld, that submissionCount appears only when canManage, the organization_not_found error and non-empty-list guarantee, and the requiresAppActivation phone-confirmation prerequisite. This is exactly the extra context annotations cannot carry.

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?

Every clause carries real information—no filler—but the telegraphic semicolon-chained style is dense and puts visibility rules ahead of a plain purpose statement. Efficient, though structure could be more scannable.

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?

Given a read-only list tool with no output schema and fully documented parameters, the description still covers visibility, permission-gated fields, error behavior, activation prerequisite, and the downstream workflow. Nothing an agent needs to call it correctly is missing.

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 q/limit/cursor/organizationId are already documented in the schema, and the description adds no format or syntax guidance for them. Baseline 3 applies since the schema does the heavy lifting.

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 makes clear this is a read of an organization's activities scoped by viewer relationship (anonymous/non-member vs member), and it distinguishes itself from list_my_activities for owners/admins. The core 'list activities of org X' statement is implied through visibility rules rather than stated as a standalone opener, which is why it is not a 5.

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?

It explicitly routes the agent: use get_organization→items.slug→get_signup_activity→submit_signup for the signup flow, and use list_my_activities / bulk_review_signup_submissions when the caller is OWNER/ADMIN/EVENT_MANAGER. That is a named alternative plus a clear exclusion condition, not just implied usage.

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