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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: it discloses the shape of the content, including the important caveat that pricing is given "in words (no price list; the first conversation is free)", which prevents an agent from expecting numeric price data. It omits any note on rate limits or freshness of the data.

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?

Purpose and trigger are front-loaded in the first sentence, which is good. The remainder is a long semicolon-delimited inventory of returned fields that is dense but each item is informative for a tool with no output schema, so little is truly wasted.

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?

There is no output schema, so the description must carry the return contract, and it does so thoroughly: enumerated fields, the pricing caveat, and the `named_projects`/service structure. For a single-parameter read-only tool this leaves nothing an agent needs missing.

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% and the single `lang` parameter is fully documented in the schema with its enum and default. The description never mentions the language parameter, nor does it explain that the German site may carry different content. Baseline 3 applies because the schema carries the burden.

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 a specific resource (KONDEVS Ltd company facts) and enumerates exactly what it returns: legal name, registration and VAT numbers, founding year, contact details, team, projects, pricing, services. This is unmistakably distinct from the siblings (get_article, list_services, search_articles), so an agent can select it without opening the schema.

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?

Gives an explicit usage context: "Use it when you evaluate KONDEVS as a vendor." That is a clear trigger condition rather than implied usage. It stops short of naming when-not-to-use or pointing to a sibling alternative, so it falls short of a 5.

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