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 useful behavioral context: the HTTP endpoint, optional project filtering, and the return envelope shape { valid, page_stats, data:[...] }. It does not cover pagination behavior, auth requirements, or rate limits, but with annotations present the added context is meaningful.

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 three compact sentences and front-loads the primary purpose. The API endpoint and return envelope notes are useful, though slightly technical for a purely informational definition; still, every sentence contributes.

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 100% schema coverage and annotations declaring readOnlyHint, the description provides enough context, including the return envelope shape. No output schema exists, but the description mentions the envelope; pagination is left to the schema, which is acceptable.

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 already documents _page, params, and project_id. The description reinforces project_id as a filter to a single knowledge base but adds no format or syntax detail beyond the schema, so the baseline score of 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?

The description states a specific verb and resource: 'List knowledge-base articles', and identifies the backing API endpoint GET /article.json. It is clearly distinct from knowledgeowl_get_article by being a list operation, though it does not explicitly name sibling alternatives or scope boundaries.

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?

The description implies usage by saying it lists articles and can optionally filter by project_id. However, it does not state when to use this versus knowledgeowl_get_article or other list_* tools, nor does it mention exclusions or conditions beyond the optional project filter.

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