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

With no annotations, the description carries full responsibility for conveying behavior. It does not mention whether the operation is read-only, side-effect-free, or requires any permissions, leaving the agent uncertain about the tool's impact.

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 extremely brief, which is concise, but it omits essential information. It is front-loaded with the verb 'Search' but fails to provide adequate context, making the brevity a drawback rather than an asset.

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?

The description is minimal and lacks any details about expected outputs, parameter usage, or the nature of the records. With no output schema and no explanation of the tool's purpose beyond a vague phrase, it is insufficient for an agent to operate correctly.

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 schema provides no descriptions for the six parameters (q, city, lang, limit, giOnly, category). The description does not explain any of them, leaving the agent without clues on how to fill them correctly.

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 states a search action on 'public regional-food records' but does not clarify what 'Yöre Sofrası' refers to or what specific records are being searched. It does not differentiate from sibling tools like 'search_places' or 'search_mavi_koy'.

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 is provided on when to use this tool versus the alternatives. The description lacks any context about typical use cases or conditions that would warrant invoking this tool.

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