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

Adds real behavior beyond the thin annotations: the pin persists across sessions, surfaces in the @-mention picker on aige.ws, and mimeType is inferred when omitted. What's missing is duplicate behavior — idempotentHint is false, so re-pinning likely creates a second entry, but the description never warns about that or about any limits on memory size.

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-loaded with purpose, then triggers, then exclusion, then Inputs/Returns headers — an agent can stop reading after sentence two and still call correctly. It is somewhat longer than necessary, with the Returns sentence partly duplicating what a caller would verify anyway.

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?

With no output schema, the description compensates by naming the return fields (fileId, label) and telling the agent to confirm the pin to the user. Combined with the stated persistence and picker visibility, nothing important about the call outcome is left unknown.

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 schema already labels every parameter; the description still adds value by stating the URL may be an HTTPS or data URL (the schema only says HTTPS) and by grouping constraints such as tags up to 8 and mimeType inference. It does not explain format expectations for label or name beyond what the schema's examples already give.

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?

Opens with a specific verb and resource: 'Pin a FILE ... to the user's long-term AIGE memory', and enumerates the asset types covered. It also explicitly contrasts itself with antix_add_to_character_gallery, so an agent can select it over that sibling without inspecting either 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?

Gives concrete user phrasings that should trigger the tool ('remember this reference', 'save this for later') plus a clear when-not with the named alternative for character reference images. The routing decision is fully specified.

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