search_iulaan

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

With no annotations, the description is the sole source of behavioral disclosure. It adds useful context by explaining that English queries are expanded into Dhivehi variants, which is a non-obvious behavior. However, it does not disclose other traits like pagination, result format, or rate limits, leaving some gaps.

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 a single, front-loaded sentence that states the core action and a key behavior. Every word earns its place, and there is no filler or redundancy.

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 has 7 parameters, no annotations, no output schema, and no parameter descriptions, this one-sentence description is insufficient. It does not explain what the parameters do, what results look like, or any additional behavior beyond query expansion, making it inadequately complete for a tool of this complexity.

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 provides no parameter-level detail. The only hint is that English queries are supported, implying the 'query' parameter accepts English, but the other six parameters are completely unexplained. The description fails to compensate for the lack of schema descriptions.

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 clearly states the tool's function: 'Search public Iulaan announcements' – a specific verb and resource. It also distinguishes from siblings like search_gazette by specifying 'Iulaan announcements' and mentions English-to-Dhivehi expansion, which is unique to this tool.

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?

The description implies usage for searching public Iulaan announcements and notes that English queries are expanded, providing clear context. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to choose this tool over siblings for Iulaan searching.

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