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

No annotations are provided, so the description must carry the burden of disclosing behavior. It offers no information about side effects, access constraints, return format, or what the preview reveals; the cryptic phrase about ReconstructUsd adds confusion rather than transparency.

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 text is short, but brevity here is under-specification, not conciseness. The second sentence is incoherent and consumes space without adding actionable information, so the structure does not earn its place.

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 required parameter, no output schema, and no annotations, the description is far from complete. It fails to explain the tool's purpose, the meaning of id, the nature of the preview, or how this relates to sibling tools.

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 0%, and the description never mentions the required id parameter, what it represents, or how it should be formatted. With a single required parameter and no semantic explanation, the agent has no basis for supplying a correct value.

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 does not state a clear verb or resource; "Public teaser for one handoff" restates the notion of preview without explaining what action occurs or what the handoff is. "ReconstructUsd is a filer estimate" is an unexplained, unrelated fragment that does not distinguish this tool from siblings such as discover, file, or status.

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?

There is no guidance on when to use preview versus the sibling tools, no context about intended scenarios, and no mention of alternatives or exclusions. The description is too vague to inform selection.

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