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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description's real contribution is the eligibility predicate (visible + available + supported destination), which explains why the result set is a subset rather than all sources. It says nothing about pagination behavior or ordering, which matters for a paged list.

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?

A single front-loaded sentence with no filler, and the eligibility constraint arrives before anything else. It is arguably too terse given the parameter surface, but there is no waste to trim.

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?

This is a five-parameter, paginated list endpoint with 0% schema description coverage and no output schema, so the description carries the full documentation burden and delivers only one sentence. An agent learns the filtering rule but not how to page, search, or filter by source type.

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 0% across five parameters, so the description must compensate and it does not: page, limit, search, sourceType and projectId are never mentioned. The one enum (sourceType, 10 values) is undocumented by meaning, and the required projectId's role is left implicit.

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 gives a specific verb (list) and resource (backlink sources) and adds qualifying scope: visible, available, and having a supported submission destination. Among siblings it is distinguishable from list_backlinks and list_available_submission_projects only by inference, since neither is named, so it stops short of a 5.

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 call this versus list_backlink_submission_projects, list_backlinks, or preflight_backlink_submission, which is the obvious next step for a newly listed source. The agent must infer the workflow entirely from the tool name.

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