hostodo_create_artifact_upload

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

Discloses return value (presigned PUT URL), validity period (15 min), and required authorization. Does not mention potential errors or rate limits, but is generally transparent for a mutation tool.

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?

Three sentences: purpose, return info, and workflow + requirements. No superfluous text, front-loaded with core action.

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?

Covers purpose, output format, constraints, and next steps. Missing details like URL format or upload method, but sufficient for correct invocation.

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?

Input schema covers all parameters with detailed descriptions (100% coverage). Description adds no extra parameter information beyond the schema, justifying baseline score.

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?

Clearly states it creates an upload slot for file transfer to a VPS, using specific verb 'create upload slot' and resource. Distinguishes from siblings like hostodo_install_artifact by describing a preparatory 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?

Explicitly describes the workflow: create slot, upload via returned URL, then install. Also specifies required scopes and prerequisites, leaving no ambiguity about when to use.

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