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

With no annotations, the description carries the full burden and largely meets it: it discloses an immediate, externally visible side effect ('immediately public'), the permission scope required, the optimistic-concurrency requirement on revision, and hard content limits (256KiB, passive shapes only, banned constructs). It does not say what is returned or whether a failed revision leaves the prior logo intact.

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?

Five tight clauses with zero filler, and the two highest-stakes facts (public immediately, revision required) come first. The telegraphic register occasionally costs readability ('Staff save/change_association') but nothing is wasted.

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 4-parameter mutation with no annotations and no output schema, the description covers side effects, authorization, concurrency and payload validity. The remaining gap is the return value and stale-revision error behavior, which nothing else in the structured data supplies.

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 0%, so the description must compensate, and it does for the highest-risk parameter: svg is defined as raw UTF-8, capped at 256KiB, and restricted to passive shapes with a list of disallowed constructs, plus the explicit exclusion of URLs and filenames. token and association_id are only implied through 'Staff ... and current revision' and the tool name, so some gap remains.

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 ('Save logo') plus the storage model ('local random SVG file') and a consequence ('immediately public'). It is distinguishable from online_association_upsert and online_association_get by scope, though it never names a sibling explicitly.

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?

'Staff save/change_association and current revision required' gives a real precondition, which is more than most. However there is no explicit statement of when to prefer this over online_association_upsert, nor any when-not guidance or mention of what happens on a stale revision.

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