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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered by structured data. The description adds only the underlying endpoint (GET /api/v2/articles), which is minor context; it says nothing about pagination behavior beyond what the schema already exposes, so it earns a baseline 3.

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 compact sentence plus an endpoint reference, with the core purpose front-loaded. Nothing is wasted, though the endpoint clause adds little for an agent that already knows the tool name.

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 read-only list tool with no output schema and full schema coverage, the description is minimally adequate. It does not mention pagination defaults or the shape of returned articles, which an agent calling a paged list endpoint would benefit from, but annotations cover the safety profile.

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 six parameters (including page, count, order_by and their bounds) are documented in the schema. The description names a subset of filters (category, status, author) but adds no format or semantics beyond the schema, which is the expected baseline when the schema does the work.

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 states a specific verb and resource ('List knowledgebase articles') and names the filter dimensions, which cleanly separates it from the singular deskpro_get_article sibling. It stops short of explicitly contrasting with other list tools (e.g. deskpro_search), so it is clear but not fully sibling-differentiated.

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 guidance on when to use this tool versus deskpro_get_article or deskpro_search, and no prerequisites or exclusions. The only usage signal is the bare phrase 'filterable by category, status and author', which implies filters exist but does not route the agent.

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