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

Annotations only declare readOnlyHint=false, openWorldHint=false, destructiveHint=false, so the description carries the burden of behavioral disclosure. It discloses the critical sequencing requirement (wait for HTTP 200 before calling upload_file), the 10-minute URL expiry, the fact that the staged entry holds no bytes until upload completes, and the failure-mode behavior (do not retry on network/DNS/allowlist errors). This is rich, actionable behavioral context beyond the annotations.

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 long but every sentence earns its place: it covers the flow, the critical wait-for-200 constraint, the expiry, and the failure fallback. It is front-loaded with the core purpose and the most important usage condition. It could be slightly tightened, but the density of critical operational detail justifies the length.

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?

For a tool with one parameter, no output schema, and minimal annotations, the description is remarkably complete. It explains the full lifecycle (stage → run curlCommand → wait for 200 → call upload_file with uploadId), the failure mode, and the fallback path. An agent has everything needed to invoke it correctly and recover from the most likely error.

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 100% and the single parameter fileName is already documented in the schema with an example. The description adds context about what the file is (a PDF attached to the conversation) but does not add new parameter-level semantics beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Stage an upload'), a specific resource (a PDF attached to the conversation), and the intended audience (clients that can execute shell commands). It clearly distinguishes this tool from upload_file by explaining the presigned URL + curlCommand flow, so an agent can tell them apart without opening schemas.

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?

The description gives explicit when-to-use guidance ('Only use this tool if you are able to run that command'), explicit when-not-to-use guidance ('if you cannot, skip it'), and names the alternatives (upload_file with `url` or with `file` as base64 plus `fileName`). It also provides a fallback path for blocked outbound requests, leaving little to inference.

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