balena_add_organization_member

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

Annotations indicate a mutating operation (readOnlyHint=false, destructiveHint=false), but the description adds no behavioral context beyond the action. It does not disclose whether the operation is idempotent (idempotentHint=false) or what happens on duplicate membership, nor does it mention permission requirements. The description adds minimal value over the annotations.

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, direct sentence that is appropriately concise for a simple tool. It is front-loaded with the core action and resource, making it easy to parse. It could be slightly more informative without becoming verbose, but overall it is 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?

Given the tool's simplicity, the description covers the basic action but lacks important context: it does not mention error conditions, return values (no output schema exists), side effects, or usage scenarios. It also fails to provide any guidance on when to use it, making it incomplete for an agent to call correctly in a real workflow.

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%, so the schema provides no parameter descriptions. The tool description also does not explain any of the three parameters. While the parameter names (organization_id, user_id, role_id) are somewhat self-explanatory, the description fails to clarify relationships or constraints (e.g., what constitutes a valid role_id for the organization). The description does not compensate for the lack of schema descriptions.

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 states the verb 'Add' and the resource 'a user to an organization', and mentions a 'membership role ID'. It clearly indicates the action and the primary resource, distinguishing it from removal tools. However, it doesn't explicitly differentiate from sibling tools like add_team_member, but the specific resource (organization) makes it clear enough.

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 such as add_team_member or remove_organization_member. It also lacks any mention of prerequisites (e.g., user must exist, role must be valid) or conditions for when this tool is appropriate, leaving the agent to infer usage.

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