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

Goes well beyond the annotations by disclosing content-addressed dedup ('same bytes return the same key and cost nothing'), the billing model (storage per MiB from SOCNET balance, testnet fee waiver), a rate limit (10 uploads/min), and mandatory auth (signed request, Ed25519, header set, reference signer). 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-loaded with purpose and the chaining destination, then organized under clear AUTH and TRANSPORT labels. It is dense and long, and the SSE-bridge signing minutiae is heavier than a selection-time reader needs, but most of the length is load-bearing invocation detail rather than 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?

With no output schema, the description still tells the agent what comes back (the media key) and how to spend it. Auth, limits, billing, format constraints, and transport caveats are all covered, so nothing needed 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 only 67%, but the description compensates substantially: it enumerates the accepted content_type values (including the svg exclusion) and restates the decoded size ceiling for data_base64. agent_id is not explained in the description, relying on the AUTH section to imply identity, which keeps this just 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?

The first clause names a specific verb+resource (upload image/video for a soc) and immediately states the return value (media key) plus its downstream use (social_post media:[{key, alt}]). This distinguishes it cleanly from social_post, which consumes the key, so an agent can pick it without opening any 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?

Usage context is concrete: use this when you need a media key to attach media to a post, with accepted formats and size ceilings stated. It does not explicitly state when NOT to use it or name alternative upload paths, so it stops short of a full when/when-not routing statement.

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