Update S3 account traffic information (s3/update_traffic_info). Available to administrators only.
Update S3 account traffic information (s3/update_traffic_info). Available to administrators only.
| Name | Required | Description | Default |
|---|---|---|---|
| s3uid | No | S3 account UID; omit only if the token is bound to a single S3 account | |
| confirm | Yes | Must be true to run the operation. | |
| account_id | No | Deprecated alias for s3uid / get_users.id |
Changes observed during successful MCP inspections.
v1.0.7Input schema / properties / account_id / descriptionPrevious value: -"Deprecated alias for s3uid"New value: +"Deprecated alias for s3uid / get_users.id"v1.0.4Input schema / properties / account_id / descriptionPrevious value: -"ID S3-аккаунта (если требуется; уточняйте через s3_get_users)"New value: +"Deprecated alias for s3uid"Input schema / properties / s3uidAdded value: +{
+ "description": "S3 account UID; omit only if the token is bound to a single S3 account",
+ "type": [
+ "string",
+ "number"
+ ]
+}v1.0.3Input schema / properties / confirm / descriptionPrevious value: -"Нужно true, чтобы выполнить операцию."New value: +"Must be true to run the operation."v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context — the admin-only auth requirement — but says nothing about immediacy of effect, what happens to unmentioned traffic settings, or how the required confirm flag gates execution.
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?
Two short sentences with the action front-loaded and the endpoint slug parenthesized for traceability. Efficient, though the parenthetical restates the tool name and consumes space that could carry actual behavioral detail.
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 mutating, admin-gated tool with a mandatory confirm parameter and no output schema, the description should explain what the update accomplishes and what to expect afterwards. The safety profile and parameter semantics are covered by structured fields, but the description leaves a real gap around what 'traffic information' means.
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 100%, so the schema already explains s3uid, confirm and the deprecated account_id alias. The description adds no parameter meaning of its own, and notably does not clarify that no parameter actually specifies the new traffic values, which is the most confusing thing about 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?
States a specific verb ('Update') and resource ('S3 account traffic information'), which distinguishes it from read-only siblings like s3_get_users and s3_list_plans. It stops short of saying what aspect of traffic is updated (quota, plan, overage), so an agent still cannot tell exactly what the mutation changes.
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 only guidance is 'Available to administrators only', which is an authorization prerequisite rather than a when/when-not rule. No alternative sibling is named and no condition for preferring this tool over s3_list_plans or s3_create_order is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.