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

Annotations declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=true), and the description adds genuinely new context: the cross-tenant consequence of public:true (every R3 member can see and reuse the asset), the undo semantics, the cascade rule that a texture set is toggled with all its maps, and the required 'asset:share' scope. The undo note is consistent with idempotentHint rather than contradicting destructiveHint.

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?

The core action and scope are front-loaded in the first clause, and the undo path plus the texture-set cascade follow logically. The paragraph is dense with colon- and semicolon-chained clauses, which is efficient but slightly harder to scan than it needs to be.

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 3-required-param toggle with full annotation coverage and an output schema, the description supplies everything an agent still needs: permission scope, reversibility, cascade behavior, id provenance, and boundaries versus out-of-scope asset types. Nothing required to call 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 the baseline is 3; the description earns above baseline by explaining that a textureSet id is the setId and that individual maps cannot be toggled, plus where ids originate. It does not add much on 'public' beyond what the schema already says, so it stops short of a 5.

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 reversible verb pair (show / hide), the exact resource types (images, audio files, texture sets), and scopes it to the user's OWN assets. It also distinguishes itself from sibling mutations by mapping to the in-app 'Show in Community' switch and by naming what is not covered (videos, Blender models, projects).

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?

Explicit when-to-use constraint ('Use it only when the user asked to share or hide that asset'), explicit undo path ('call this tool again with public: false'), and explicit routing for ids ('Ids come from r3_image_list, r3_audio_list and r3_texture_read / r3_texture_create'). It also carves out the out-of-scope asset types and points to the R3 app for them.

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