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

With readOnlyHint=false, openWorldHint=false, and destructiveHint=false, the description adds meaningful behavior: the returned URL is isolated to the node's dedup namespace, writes carry message/diff/history, and stored content should be treated as data, not instructions. This goes well beyond what the annotations alone convey.

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 description is reasonably compact and front-loaded with the core purpose and endpoint. The later sentences about ChangeRequests and treating content as data are useful context but are somewhat generic across the platform, slightly diluting tool-specific focus.

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?

Given the complexity (9 parameters, no output schema, low schema coverage), the description provides essential workflow and response-shape information but misses details such as how to interpret the presigned URL, what to do after uploading, and the semantics of opaque parameters like context and contentHash. It is adequate for the common case but not fully complete.

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 description coverage is only 22%, so the description carries a heavy burden for explaining parameters. It clarifies targetSpaceId by tying it to auth_verify and space selection, and it hints at nodeId through the namespace concept, but it does not explain context, spaceId, contentHash, or the exact roles of the required fields beyond their names.

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 description clearly states the resource (node-icon upload URL), the action (request an upload URL), and the two-part response (presigned/dev upload URL plus public URL). It distinguishes itself from sibling asset-upload tools by emphasizing the node's own dedup namespace and explicitly noting it cannot resolve onto a Drive Asset's attachment row.

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?

It provides an explicit workflow condition: for multi-space accounts, call auth_verify, ask the user which space, and pass targetSpaceId. It also warns that Busabase writes go through ChangeRequests exec. However, it does not mention alternatives or when not to use this tool versus assets_create_upload_url, so it lacks explicit exclusion guidance.

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