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

Annotations already carry the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false), so the bar is lowered, but the description adds nothing beyond the purpose. It does not state what permissions are needed, whether re-granting is safe, or what happens on conflict.

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?

A single front-loaded sentence with no filler, which is structurally clean. But the terseness borders on under-specification for a mutation tool with four parameters and a nested object.

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?

An output schema exists, so return values need not be explained, but for a non-idempotent mutation with 4 undocumented parameters and no annotations covering auth requirements, the definition is too thin to guide a correct call.

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% across 4 parameters, including a nested body object with three required fields. The description only loosely gestures at 'role' and 'scope' and leaves sub, tenant_id, and authorization entirely unexplained, so it fails to compensate for the coverage gap.

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?

States a specific verb ('Grant') and resource ('role x scope assignment') plus the target ('tenant member'), so an agent can tell it is an authorization-granting tool. However, it never names revoke_assignment for differentiation, and the 'role x scope' phrasing is idiosyncratic.

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?

There is no when-to-use context, no mention of prerequisites such as the required authorization token, and no reference to alternatives like revoke_assignment or create_access_request. The agent gets no routing help beyond the one-line purpose.

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