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

The description reports a mutating, destructive behavior: it 'Replaces any prior logo and deletes the old file from storage'. The annotations declare readOnlyHint=true and destructiveHint=false, which directly contradicts that. Per the rubric this is an annotation contradiction and scores 1, even though the description itself is the more informative half.

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?

Three tight sentences with the action front-loaded, followed by a scannable metadata block. Slight redundancy: the `data:image/<png|jpeg|svg+xml|webp>` enumeration restates the schema's pattern, and the bracketed metadata is boilerplate rather than description content.

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 no explanation, and the key mutation facts (overwrite + delete of the prior file, size cap, 10-credit Tier 1 cost) are disclosed. Still missing for a 3-parameter write tool: permission/auth requirements and any explanation of the two undocumented compaction parameters.

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 67%, so the schema carries part of the load. The description does add real meaning for the required data_url beyond the regex (the 512 KB limit, the readable format list), but it says nothing about `fields` and `precision`, which look like copy-pasted compaction parameters with no stated role in a logo upload.

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 ('Upload a logo') plus the accepted format, the 512 KB ceiling, and the overwrite semantics. Among the white-label siblings (astroway_whitelabel_config, astroway_whitelabel_domain_verify, astroway_whitelabel_preview) an agent can tell immediately that this one sets the brand mark rather than configuring or previewing it.

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?

Usage is only implied: the [Group: White-label] and [Endpoint: POST /v1/whitelabel/logo] metadata make the context clear, but there is no explicit when-to-use, no statement of prerequisites (must the white-label be configured or the domain verified first?), and no routing to or away from the sibling whitelabel tools.

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