Search statistical releases

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: unfiltered calls return the newest releases, and every result carries an id that feeds am_release or am_table. It does not mention rate limits, auth, or result size beyond the schema's 25-per-page, which keeps it just short of 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?

Three sentences, front-loaded with the verb and resource, then usage, then next steps. The enumeration of six ready-made tools is long but earns its place as a routing shortcut; otherwise there is no filler.

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 an 8-parameter, all-optional search tool with no output schema, the description covers default behavior, the key result field (id), and the handoff to am_release and am_table. The shape of a result beyond its id is left implicit, which is the main remaining gap.

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%, so the schema already documents every parameter, including the Persian-language query hint and the enum meanings. The description restates the query language and explains that source and data_type narrow by the portal's own system and type, but it leaves the overlap between kind and data_type unresolved, adding little beyond the schema.

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: search the Statistical Centre of Iran catalog of releases (tables, time series, reports). It also distinguishes itself from siblings by naming am_release and am_table as follow-ups and listing the ready-made tools (am_inflation, am_labour_force, etc.) that make searching unnecessary.

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?

Gives explicit when-to-use conditions (find a release by Persian title words, year, publication frequency, type) and an explicit alternative path: 'Ready tools need no search' followed by the concrete tool names. It also says what happens with no filters and which tool to call with the returned id, so routing is fully determined.

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