get_resource_info

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

No annotations provided, so description carries full burden. It discloses returns (format, size, URL) and warns about large files. It does not mention authentication or rate limits, but these are likely irrelevant for a public open data platform. Overall, behavior is sufficiently transparent for a read-only operation.

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?

Description is three sentences, all essential. First sentence states purpose, second gives usage and return list, third adds important caution. No redundant information; front-loaded with key 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?

Given the tool's simplicity (one required parameter, output schema exists), the description covers return values, usage, and a caution. It lacks explanation of the parameter's source, which is a minor gap. Overall, it provides nearly complete context for an agent.

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%, so description must explain the sole parameter 'resource_id'. However, it only states 'for a specific data file' without clarifying what a resource_id is or how to obtain it (e.g., from get_dataset_info or search_datasets). This lack of parameter context reduces usability.

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?

Description clearly states verb 'Get' and resource 'file format, size, and direct download URL for a specific data file on opendata.az'. It distinguishes from sibling tools (get_dataset_info, search_datasets) by focusing on file-level details rather than dataset metadata or search.

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 states when to use: 'Use this when the user needs to download a file or get the link.' Also provides a critical usage warning: 'Do not load large files into context—instruct the user to download from the URL or use the URL in code to fetch locally.' This gives clear context for appropriate use.

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