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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds one behavioral fact beyond the annotations: the response is delivered as Markdown. It says nothing about auth needs, rate limits, error behavior for a bad slug, or fallback when an identifier is missing.

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?

Two short sentences, front-loaded with the return shape before the identifier guidance. The trailing Russian duplicate ('/ Полное описание работы') is pure restatement and earns no place in an English-facing decision, which keeps it from a 5.

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?

With no output schema, the description carries the return-value burden and does so by naming the format and payload ('Full case description ... as Markdown'). Combined with the four identifier parameters and the safety annotations, an agent has enough to call it correctly; only the identifier-selection nuance (which of id/slug/url to prefer) is left unstated.

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 all four parameters (id, url, slug, lang) are already documented in the schema, including the lang default and the 'English exists only for translated pages' caveat. The description only restates that id, slug or url may be passed and omits lang entirely, so it adds little beyond the schema.

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 verb and resource ('Full case description of one project'), clearly a single-item fetch rather than a listing, which implicitly contrasts with list_portfolio/get_service. It does not name a sibling alternative, but the singular scope is unambiguous.

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?

The phrase 'Pass id, slug or url' implies this is used after obtaining an identifier from a list result, which is useful implied guidance. However, there is no explicit when-to-use/when-not statement or mention of alternatives such as list_portfolio or search_content, leaving routing to inference.

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