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

Adds genuinely useful context beyond the annotations: the return value (invitation URL), the default email side effect, and retry semantics tied to idempotency_key. The retry-safe claim sits alongside idempotentHint=false, but the description clarifies that deduplication comes from the client-supplied key rather than inherent idempotency, so this is not a 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?

Three tight sentences: purpose first, then the email default, then retry behavior. No filler and every clause conveys a decision-relevant fact.

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 9-parameter mutation tool with no output schema, the description covers the headline side effect, return value, and retry behavior, but leaves role choice and several parameters unexplained while the schema covers only a third of them.

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 only 33% schema description coverage across 9 parameters, the description should carry more of the burden. It explains send_email and idempotency_key semantics but says nothing about the role enum (admin/member/client), brand_id, email format expectations, or the confusing workspaceId vs workspace_id duplication.

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 (Invite) and resource (member/client to a workspace), which cleanly separates it from siblings like aidelly_add_creator, aidelly_update_workspace_member, or aidelly_create_workspace. The agent can identify the operation without opening the schema.

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?

Gives a clear behavioral condition for use – by default the invite is emailed, and send_email=false creates it silently – which tells the agent how to pick the right invocation. It does not, however, mention adjacent tools (update/remove member, revoke invitation) or the prerequisite of valid admin permissions.

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