manage_link_invitations

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

With no annotations, the description must disclose behavioral traits, but it only says 'manage'. It does not explain side effects (e.g., whether linking creates an invitation, requires approval, or is reversible), permissions needed, or what happens on success/failure. This is a significant gap for a mutation tool.

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 short sentence, but it restates the tool name without adding informative content. Conciseness is not valuable when the sentence does not earn its place; it provides no insight beyond what the name already conveys.

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 3 required parameters, no annotations, and no output schema. The description fails to explain return values, side effects, or the expected workflow. This is completely inadequate for an agent to understand the tool's behavior and invocation correctly.

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?

The description adds no information about the parameters. The schema covers customerId and targetCustomerId with descriptions, but the action parameter lacks a description and the tool description does not clarify the relationship between the parameters or the meaning of LINK/UNLINK. With 67% schema coverage, the description should compensate for the missing 'action' semantics but does not.

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 'Manage account linking invitations' is essentially a restatement of the tool name 'manage_link_invitations'. The verb 'manage' is vague and does not specify the concrete actions (LINK/UNLINK) or the resource beyond what the name already implies. It lacks the specificity needed to clearly distinguish it from other management tools.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical scenarios, or exclusions. Since there are many sibling tools, this absence of context leaves the agent without direction on whether this tool is appropriate for a given task.

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