Verzeichnis hochladen (mit Beweis-Wanderung)

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

Explicitly discloses that after upload, files are compared using SHA-256, size, or skipped. Annotations indicate idempotentHint=true, consistent with verification. No contradiction.

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?

Two concise sentences: first states the action, second explains the proof parameter. No unnecessary words.

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, and description does not mention what is returned (e.g., success/failure, comparison results). For a complex operation, this information is missing, reducing completeness.

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 covers all parameters with descriptions (100% coverage). Description adds meaningful detail for the proof parameter, explaining each enum value (hash=sha256, size, none). localDir and remoteDir are straightforward.

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 uploads a local directory recursively and verifies files based on the proof parameter. Differentiates from siblings like upload_file (single file) and download_dir (download direction).

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?

Describes the core function well, implying use for directory uploads with verification. Does not explicitly contrast with alternative tools (e.g., upload_file for single files), but the context of sibling tools makes it clear.

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