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

Annotations already establish that this is a safe read operation, so the description's main added value is semantic. It discloses that the response includes the person's answer, places, and offers, and it gives a specific, non-obvious caveat about ifOthersCount being a count of people not coming and not to be added to coming counts.

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 short and front-loads the core read operation before adding the ifOthersCount warning. Every sentence carries relevant information, though the warning could be phrased more cleanly.

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 read tool with three parameters and no schema descriptions, the description leaves the parameters entirely unexplained. Annotations cover safety, but an agent still lacks guidance on identifiers, token semantics, and return structure beyond a brief mention of answer, places, and offers.

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%, yet the description says nothing about token, spaceId, or activityId. It does not explain what identifiers are required or how the optional token affects the read, so it fails to compensate for the missing parameter documentation.

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 read operation over a person's activity participation data: their answer, places, and offers. It is clear enough to distinguish from write-oriented siblings like activities_answer or activities_update, but it does not explicitly differentiate itself from read siblings such as activities_get_choice.

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 no guidance on when to use this tool versus alternatives like activities_get_choice, activities_list_join_requests, or activities_answer. The warning about ifOthersCount is a data-interpretation rule, not a usage guideline.

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