generate_password_link

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

No annotations exist, and the description only labels it as a 'mutation' without disclosing side effects, whether it sends an email, how the generated link behaves, expiration, or required permissions. The description carries the full burden and fails to provide any behavioral detail.

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 cluttered with a variable list and a long truncated example, making it difficult to parse. It lacks clear structure, and the example is cut off mid-sentence, reducing usefulness.

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?

This is a mutation with 14 parameters, no annotations, and no output schema, yet the description only provides a name and a parameter dump. It does not explain the tool's purpose, outcomes, or edge cases, making it clearly insufficient for an agent to select and invoke 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?

Schema descriptions cover all 14 parameters, but they are only GraphQL type labels (e.g., 'GraphQL: String' or 'GraphQL: ID!') that don't convey semantic meaning. The description adds an example JSON with filter structure, which gives some context, but the example is truncated and many nested types remain unexplained. Since coverage is technically 100%, the baseline is 3, and the example provides marginal additional value.

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 restates the tool name as 'mutation generatePasswordLink' and adds no verb or resource explanation. It lists variables and an example but never says what the tool actually does (e.g., generate a password reset link for a user). This is essentially a tautology with some parameter metadata.

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?

No context is provided about when to use this tool over related user-management tools (e.g., resend_invite, send_forgot_password, update_user). There are no alternatives, prerequisites, or exclusions mentioned.

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