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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful eligibility constraint of 'visible, available' sources with a supported submission destination, but omits pagination behavior, auth requirements, or result ordering details.

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?

The description is a single front-loaded sentence with no wasted clauses. It is appropriately concise, though the phrase 'visible, available' is slightly redundant and the overall brevity may be under-informative for the tool's parameter surface.

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?

Given five parameters, 0% schema description coverage, no output schema, and pagination/filter capabilities, the description is incomplete. It states what is listed but omits any explanation of filtering, pagination, required project context, or the sourceType enum, leaving the agent with insufficient invocation guidance.

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% and there are five parameters, yet the description mentions none of them (projectId, page, limit, search, sourceType). It provides no compensation for the completely undocumented parameters, including the required projectId and the sourceType enum.

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 uses a specific verb and resource ('List ... backlink sources') and adds a clear eligibility condition ('that have a supported submission destination'), distinguishing it from general backlink listing. It does not explicitly name sibling alternatives like list_backlinks or list_backlink_submission_projects, but the purpose 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?

There is no explicit guidance on when to use this tool versus alternatives such as list_backlink_submission_projects or create_backlink_submission. The eligibility wording implies context but leaves the agent to infer when this list, rather than another sibling, is appropriate.

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