Get one release

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description still adds real behavioral context: the mix of file formats returned, the need for the agent to fetch PDF links externally, and the error behavior for delisted releases. It stops short of describing pagination or field completeness, keeping it a 4 rather than a 5.

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 short paragraphs with zero filler: the first states what is returned, the second states when to call it and what to do with the output. The most decision-relevant line ('Use it after am_search') is front-loaded.

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?

With one required parameter, no output schema, and read-only annotations, the remaining burden is telling the agent what a release contains and how to consume its files — and the description does exactly that. Nothing needed to call it correctly is missing.

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 coverage is 100% and the schema already documents 'id' as a release id from am_search with an example, so the description cannot add much. Its only extra signal is that the same id is what you pass onward to am_table, which is a useful chaining hint but marginal. Baseline 3 applies.

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?

States a specific verb and resource ('Get one statistical release from amar.org.ir') and enumerates what comes back: title, topic path, period, downloadable files. That distinguishes it cleanly from am_search (which discovers releases) and am_table (which reads their Excel payloads).

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 sequences the tool: 'Use it after am_search,' and routes each file type to its consumer ('read an Excel file with am_table (passing this id), open the PDF link yourself'). It also flags a failure mode — a removed release returns an error — so the agent knows how to interpret that outcome.

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