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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral content by enumerating the returned statistics (total, translated, fuzzy, percent, last change), which is valuable given there is no output schema. It stops short of describing pagination behavior or the next_page contract.

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?

One tight sentence front-loads the resource, scope, and returned fields, followed by the raw GET path. Efficient with no filler, though the path is somewhat redundant for an agent that does not construct URLs directly.

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 4 parameters, 100% schema coverage, and no output schema, the description supplies the otherwise-missing picture of the reply shape. It omits pagination semantics, which live in the schema, and does not relate itself to the adjacent list/get tools, but nothing essential for a correct call is 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%, so the schema fully documents project, component, page, and page_size slugs and ranges. The description adds no format or constraint detail beyond that, so the baseline 3 applies.

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 (List) and resource scope (translations of a component, one language each), plus the exact fields returned. This is distinguishable from siblings like weblate_list_languages, weblate_list_project_languages, and weblate_get_translation because the scope is a single component's per-language translation records.

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?

Usage is implied by the clearly scoped resource: call this to enumerate the languages a component is translated into with stats. However, no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as weblate_list_project_languages or weblate_get_statistics for narrower/broader views.

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