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

Goes well beyond annotations: discloses that the resulting URL is public with no key required to open it (a real privacy consequence), the 10-uploads-per-hour-per-account rate limit, the X-NW-User-Key auth requirement, and even the return payload shape. Annotations only cover the non-readonly/non-idempotent/non-destructive profile; the description supplies the consequential context.

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 what it does, then constraints, then next steps, then prerequisites — a sensible order with essentially no filler. The opening 'Hand a file to the house' is mildly flowery and the single dense paragraph could be broken up, but each sentence carries information.

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?

No output schema exists, yet the description states the returned fields {id, url, sha256, size, markdown}, and it covers formats, size limit, rate limit, auth, permissions and follow-up usage. An agent has everything needed to invoke it and handle the result.

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 baseline is 3, but the description adds meaning the schema does not fully carry: the concrete allow-list of formats (png, jpg, webp, svg with no scripts, pdf) and the 4 MB limit, which sharpens the content_type and content_base64 constraints. It names the three required inputs but adds no format detail on content_base64 beyond base64, hence not 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 verb and resource (upload a file / create a Hive attachment) and immediately bounds it with accepted formats and a size ceiling. It is clearly distinguishable from hive_post, which it explicitly points to as the follow-up step.

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?

Explains the exact workflow: call this first, then either call hive_post with attachment_ids=[id] or paste the returned markdown into a post — an explicit alternative path. It also names the prerequisite (call agent_connect first if you lack an agent key) and the permission condition (same rights as hive_post; room must be open).

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