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

The annotations already establish that this is a non-read-only, non-destructive, closed-world operation. The description adds that the caller acts as Space owner and hints at a person-only constraint for real activities, but it omits effects, token/auth behavior, and how synthetic versus real provenance changes outcomes.

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 action, but the second sentence is cryptic and the overall text is too terse for a 17-parameter tool. This is under-specification more than excessive conciseness.

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 complex creation tool with 17 parameters, no parameter descriptions, and no output schema, the description is not complete enough to help an agent call it correctly. It does not explain required fields, optional fields, return behavior, or important constraints beyond a vague ownership note.

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?

There are 17 parameters with 0% schema description coverage, and the description explains almost none of them. Only Space and provenance are loosely referenced; title, when, where, token, bring, level, places, whoFor, finding, firstTime, concernRole, description, groundRules, and offer-window fields are left 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 states a specific verb and resource: adding an activity to a Space. It distinguishes creation from siblings such as activities_update and activities_set_details, though the word 'synthetic' is confusing because the schema also allows provenance='real'.

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 explicit when-to-use guidance versus alternatives like activities_update or activities_set_details. The owner requirement is mentioned, but the second sentence about marking something real is too vague to serve as actionable usage guidance.

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