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

The description explicitly says the upload 'replaces any prior logo and deletes the old file from storage' — a write/destructive side effect — while the annotations declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. This is a direct contradiction between the stated behavior and the structured safety profile.

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 tight sentences with the format constraint front-loaded, plus brief group/cost metadata. Nothing is padded, though the bracketed metadata lines add little for an invoking agent.

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?

An output schema exists so return values need not be explained, and the description covers format, size, and side effects. However, it omits auth/permission requirements and error behavior (invalid image, oversized payload), and its side-effect disclosure conflicts with the annotations instead of clarifying them.

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 67% and the description fills the main gap: it spells out the base64 data-URL shape and the 512 KB size ceiling for data_url, which the schema only encodes as a regex. The unrelated 'fields'/'precision' compact-mode params are documented in the schema, so nothing critical is missing.

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 a specific verb and resource: uploading a white-label logo, with the accepted data-URL format enumerated. It does not explicitly contrast itself with siblings like astroway_whitelabel_config or astroway_whitelabel_preview, but the resource is unambiguous enough to route correctly.

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?

It never says when to use this tool versus the other white-label siblings, nor what prerequisites (e.g. branding config existing) or exclusions apply. The format constraints are payload requirements, not usage guidance, so the agent must infer the context on its own.

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