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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the useful non-obvious scope constraint that results are limited to pending applications, but says nothing about pagination defaults, result ordering, or what happens when the page is out of range.

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 purpose and the scoping qualifier before the API mapping. The 'Dub: GET /partners/applications' clause is mildly redundant but cheap and occasionally useful for API lookup.

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?

For a simple, zero-required-parameter read-only list this is close to adequate, but with no output schema the description could have sketched what an application record contains or that pagination metadata is not returned alongside, leaving the agent to infer the response shape.

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%, with page and pageSize fully described including bounds, so the baseline is 3. The description contributes no additional parameter meaning such as defaults or sensible values.

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 (partner applications) with a scoping qualifier (pending), which separates it from dub_list_partners. It does not explicitly name or contrast that sibling, but the resource noun is distinct enough that an agent can route correctly.

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 when-to-use guidance, no mention that the sibling tools dub_approve_partner_application and dub_reject_partner_application operate on the records this tool returns, and no note that only pending (not approved/rejected) applications are surfaced as a filter. Usage is implied by the name and 'pending' qualifier only.

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