Get Dataset Download Plan

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'without writing files' implying read-only, but doesn't explain what a 'plan' entails, whether auth is required, or what happens if auth is missing. The phrase 'including local provider-auth guidance when required' is vague and doesn't describe output or side effects.

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 short but under-specifies. It uses jargon like 'trusted OpenConstruction metadata route' without explanation, so brevity is not conciseness; it's vague.

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 that likely returns a download plan, there is no information about output, preconditions, or why to use it over download_dataset. The description is inadequate for an agent to understand what it does or when to invoke it.

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?

The only parameter is dataset_id, and the description does not mention it at all. Schema coverage is 0%, so the description must compensate but offers no explanation of how dataset_id is used.

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 uses vague terminology like 'Resolve the trusted OpenConstruction metadata route' without specifying what a download plan is or what the tool concretely returns. It does mention 'without writing files' which hints at a non-destructive operation, but the purpose is not clearly differentiated from siblings like download_dataset or get_download_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?

No guidance on when to use this tool versus the siblings (e.g., download_dataset, get_download_status). It does not state prerequisites, conditions, or scenarios where this plan would be needed before an actual download.

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