list_articles

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

No annotations provided. The description says 'list' implying read-only but fails to disclose any behavioral traits such as idempotency, rate limits, or data freshness beyond the basic operation.

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?

Single, clear sentence with no unnecessary verbiage. It efficiently conveys the core purpose and optional filters.

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?

Adequate for a simple list operation with optional filters. However, missing details about return order, pagination, meaning of lifecycle status, and any prerequisites (e.g., project existence). Output schema exists but description could add context.

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?

With 0% schema description coverage, the description adds meaning by explaining that status filters by lifecycle status and project_id filters by project, but does not explain the limit parameter or provide enums/values for status.

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 clearly states the tool lists generated articles with optional filters by project and lifecycle status. It distinguishes from siblings like get_article (single article) and generate_article.

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?

Implies usage for listing articles with filters but no explicit guidance on when to use versus alternatives (e.g., get_article) or conditions for not using.

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