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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that consent can be granted or revoked, but does not mention consequences of revocation, version-based concurrency via expectedVersion, idempotency guarantees via idempotencyKey, or whether existing data is affected.

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 a single front-loaded sentence with no filler; every word earns its place. However, it is concise at the expense of essential parameter and behavior context, so it does not fully serve the agent despite its brevity.

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?

The tool has a nested versioned consent object, three required parameters, no output schema, and no annotations, yet the description covers only the high-level purpose. It omits return behavior, validation or concurrency semantics, and the workflow context in which consent should be granted or revoked.

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?

With 0% schema description coverage and a nested consent object, the description must compensate. It clarifies that consent and exportConsent map to participation and dataset export consent, but id, expectedVersion, and idempotencyKey remain unexplained. The description adds partial meaning but is insufficient for correct invocation.

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 uses a clear verb plus resource: 'grant or revoke' 'your participation and separate dataset export consent.' This precisely distinguishes the tool from siblings like invite_research_participant (which concerns inviting others) and prepare_research_export (which concerns preparing exports rather than consent).

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it explain prerequisites or when revocation is appropriate. It identifies the action but not the conditions that should trigger it, leaving the agent to infer context from the tool name.

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