direct_list_businesses

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and 'Read-only' in the description merely repeats that. The only added behavior, that Phone/Address are omitted by default, implies an include-switch that the schema does not actually expose, so it borders on misleading with no pagination or auth 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?

It is short and front-loads the resource and fields, which is good. But the brevity is under-specification rather than economy: whole sentences are missing on inputs and paging for a tool that has three unfiltered-when-omitted parameters.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What is missing is any guidance on the three inputs or pagination behavior, leaving an agent unable to use ids/limit/offset correctly from the definition alone.

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?

Three parameters (ids, limit, offset) exist at 0% schema description coverage, and the description mentions none of them — not the meaning of ids filtering, not the default limit of 500, not offset paging. The description describes the response entity rather than the inputs, so it fails to compensate for the coverage gap.

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 names the resource (Yandex Business profiles) and enumerates the returned fields (Id, Name, IsPublished, Rubric), so the agent knows roughly what comes back. However, the verb is only implied by the tool name, and there is no differentiation from the many other direct_list_* siblings. Adequate but not sharp.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for related queries. The 'no Phone/Address by default' clause hints at scope but never tells the agent when this listing is the right call.

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