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

Annotations flag destructiveHint=true and idempotentHint=true, but the description goes further and specifies the exact blast radius: all existing 'email' allowlist entries of this code are replaced while domain/glob entries stay untouched. It also discloses the required permission (can_manage_scope=1), which annotations cannot express.

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 destructive scope and the permission requirement are front-loaded in the first two clauses, which is the right order. The trailing '| EN: allowlist, permission, whitelist, code' keyword block is search-noise that adds nothing for an agent and slightly dilutes the message.

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 3-parameter destructive mutation with no output schema, it covers purpose, destruction scope, workflow context and permissions. It omits the return shape (imported/rejected counts) and error behavior on invalid files, which an agent would need to report results 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 coverage is 100%, so the baseline is 3, but the description adds real meaning by indicating the file should carry e-mail addresses (e.g. 500 subcontractor addresses) and implying code_id targets a single invite code. It still doesn't describe row-level validation or what happens to malformed rows in file_base64.

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 and resource (bulk XLSX/XLS upload for the e-mail allowlist of a scope invite code) and quantifies typical scale. It is clearly distinguishable from siblings add_code_allowlist_entry (single entry) and list_code_allowlist (read), which an agent can infer without opening any 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?

Names the intended workflow (weekly full re-upload) and the precondition can_manage_scope=1 on the code's scope, which is exactly the gating an agent needs. It does not explicitly name add_code_allowlist_entry as the alternative when the intent is to add rather than replace, so it stops short of full when/when-not routing.

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