Agregar usuario a un scope

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

There are no annotations, and the description does not disclose side effects, idempotency, required permissions, or behavior when the user is already in the scope. The description only states the basic operation without additional behavioral details.

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 clear sentence, front-loads the main action, and includes a concise parenthetical for a special case. It is appropriately sized and well structured.

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 description does not mention return values, potential errors, whether the user must exist in the system, or what happens on duplicate assignment. The unexplained 'extra' parameter also contributes to incompleteness. Given the lack of annotations and output schema, more context is needed for an agent to fully understand the operation.

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 input schema already provides descriptions for 'username' and 'idScope', including the special meaning of idScope 0. The tool description repeats this idScope guidance but adds no further parameter semantics. The 'extra' parameter remains unexplained, so there is no additional value beyond the schema.

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 clearly states the action: 'Agrega un usuario existente a un scope' (Adds an existing user to a scope). It specifies the verb and the resources involved, and the parenthetical about idScope 0 clarifies an important input variation. This distinguishes it from siblings like remove_user_from_scope.

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 does not explicitly state when to use this tool over alternative tools such as assign_user_roles or remove_user_from_scope. The usage is implied by the name and description but lacks explicit when-to-use or when-not-to-use guidance.

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