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

Annotations only declare the mutation/safety profile; the description adds login requirement, synchronous size/format/SSRF/image-safety validation, rejection criteria for avatars with QR codes or contact info, and the non-idempotent retry caution — substantial context beyond structured fields.

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?

Information-dense with a front-loaded login requirement and compact bracketed groupings; almost every clause carries actionable meaning. The density is high but structured rather than padded.

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 write tool with no output schema, the description covers prerequisites, validation behavior, rejection handling, format limits, and the follow-up composition chain (write the returned URL onto the target object). Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, but the description adds meaning beyond the schema: avatar triggers contact-info/QR rejection and moment-image carries a JPEG/PNG/WebP format constraint not stated in the schema's kind description. It clarifies how kind affects acceptance.

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: mirroring a public HTTP(S) image to a stable URL, with the synchronous validation performed. It is clearly distinguishable from the many prepare_*_upload and set_organization_logo siblings.

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 gives explicit conditions and alternatives: use fetch_organization_logo for organization logos rather than fabricating a URL, do not retry a rejected avatar but swap the image, and restricts moment-image to JPEG/PNG/WebP. When-to-use and when-not-to-use routing is spelled out, not inferred.

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