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

Annotations already cover safety hints (non-destructive, idempotent, open-world). The description adds important context beyond annotations: login requirement, required capability, maximum of 50 picks, and clarification that the activity itself is not modified. It does not cover error behavior or full permission boundaries.

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?

The description is dense but well-structured, front-loading the login/capability requirement and then the boolean semantics, followed by usage guidance and constraints. Every sentence carries useful information, though it could be slightly 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?

For a mutating tool with no output schema and zero schema description coverage, the description supplies auth requirements, capability requirement, boolean effect, idempotency, and a limit. It omits error cases and detailed ID sourcing, but is otherwise sufficient for correct invocation.

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% for all three required parameters. The description explains the meaning of picked (true adds to alliance, false removes) and implicitly references organization and activity, but adds no format or sourcing detail for organizationId and activityId. It partially compensates but leaves ID semantics 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?

The description states a specific verb (pick/unpick) and resource (organization activity), and explains the effect of picked=true versus false. It also clarifies that the activity itself is not changed, which distinguishes it from update tools.

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 gives clear prerequisites (login required, pickActivities capability) and advises confirming organization, activity, and intent before calling. It does not name alternative tools or explicit when-not-to-use conditions, but the context is sufficient for selection.

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