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

The description says the tool refuses for AIs and never answers for them, which directly contradicts the annotations (destructiveHint=true, readOnlyHint=false) and the schema requiring an 'answer' parameter. This is an annotation contradiction.

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?

Two short sentences with no wasted words, and the refusal is front-loaded. The phrasing is unusual but structurally efficient.

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 tool with five parameters, three required, a destructive annotation, and no output schema, the description is far too thin. It explains the refusal policy but not what happens on invocation, how parameters are used, or what is returned.

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% and the description mentions no parameters. It does not explain spaceId, activityId, the answer enum values, others, or token, leaving all five parameters undocumented.

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 does not state a clear action; it declares the tool 'Refused for AIs' and explains a policy rather than what the tool does. It distinguishes from activities_participation by directing there, but the actual purpose of activities_answer remains ambiguous.

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 says never answer for them and to tell the person what activities_participation shows, which is clear guidance to avoid this tool and use the sibling. It does not state any scenario where activities_answer should be called, but the prohibition is explicit.

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