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

The description only says 'Fetch' without disclosing side effects, error behavior, or confirmation that it is read-only. Since there are no annotations, the description bears the burden but does not provide this context.

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 concise with no unnecessary words. It front-loads the action and object, making it easy to parse.

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 important context such as the meaning of the lang parameter or expected output. Given the simplicity of the operation, the missing parameter explanation leaves gaps for correct usage.

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 slug parameter is implicitly defined by 'by slug', but the lang parameter is not mentioned at all. The enum values (tr/en) are present in the schema but the description does not clarify their purpose or effect on the result.

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 fetches a single dish by slug, using a specific verb and object. It distinguishes itself from search_dishes by indicating it fetches one specific dish rather than searching.

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 alternatives like search_dishes. The description does not mention contexts where fetching by slug is preferred or when not to use it.

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