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

Annotations already declare readOnly=true, idempotent=true and non-destructive, so the safety profile is covered. The description adds two useful facts: results are filtered to 'visible' companies, and the rows mirror the GET /api/v1/companies/by-city endpoint. It says nothing about ordering or pagination behavior, so it only modestly exceeds the annotation baseline.

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?

Short and front-loaded, but the description is repeated verbatim in Hebrew with no added information, and the endpoint-reference sentence is cryptic without elaboration. Roughly a third of the text does not earn its place.

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 a read-only, single-filter list tool with 100% schema coverage and no output schema, the basics are present and the endpoint parity note is a useful hint. However, nothing is said about result ordering, total counts, or how the pagination window behaves, leaving real gaps for agent planning.

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 city, limit and offset are fully documented in the schema itself. The description adds no parameter detail beyond what the schema already provides, making 3 the baseline.

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 the resource (companies) and the scoping filter (one city), which clearly distinguishes it from siblings like list_companies_by_type and list_companies_by_year. The word 'visible' is left unexplained, mildly clouding the scope.

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 indication of when to use this versus search_companies or the other list_* siblings, and no stated prerequisites. The agent must infer selection from the name alone.

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