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

Goes well beyond the annotations (idempotentHint, destructiveHint=false) by disclosing that the server fetches and re-hosts the image, runs machine moderation that can reject QR codes or contact-driving images, deletes rejected images immediately, returns 'image_content_rejected', enforces jpg/png/webp ≤5MB public direct links, and blocks edits to archived orgs. This is exactly the operational context annotations cannot carry.

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?

Front-loads the auth requirement and core action, then uses bracketed labels (【组合链】, 【口径/坑】) to group workflow routing and pitfalls. Every clause in the ①②③ list carries distinct, non-redundant information; nothing is filler.

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 two-parameter mutation tool with no output schema but a full annotation set, the description closes every gap: permissions, input validation, error code, moderation behavior, idempotent removal semantics, and the archived-org edge case. An agent has everything needed to call it correctly or explain a failure.

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 constraints the schema does not encode: acceptable formats, 5MB limit, public direct-link requirement, and the null-equals-removal/avatar-fallback behavior. The OWNER/ADMIN requirement also qualifies the organizationId parameter's authority context.

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?

Names a specific verb and resource ('按图片链接给组织换 logo') and immediately defines the scope, including the null case that removes the logo and falls back to the initial-letter avatar. An agent can distinguish this from generic siblings like update_organization or upload_image_from_url without opening the 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?

The 【组合链】 section explicitly routes the agent: image URLs come from the user or from upload_image_from_url's output, then feed this tool. It also states the auth precondition (login + OWNER/ADMIN). It stops short of naming when *not* to use it or pointing to an alternative for other org-field edits.

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