list_news

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

No annotations present, description reveals limit cap and pagination behavior. Does not disclose read-only nature, auth requirements, or edge cases (e.g., empty results). Adequate but not fully transparent.

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 concise sentences, front-loaded with purpose, followed by key behavioral detail. No redundant or irrelevant information.

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?

Covers core functionality and pagination, but omits response structure, ordering, and error conditions. Given no output schema, more context on return value would be beneficial.

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 coverage, description adds meaning to all parameters: project and search as filters, limit capped, offset for paging. But lacks format details (e.g., project ID vs name) and default values beyond the cap.

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?

First sentence clearly states verb and resource: 'List news entries' with optional filters. Distinguishes from sibling 'get_news' which fetches a single entry, though not explicitly.

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?

Provides explicit context for filters and pagination: 'optionally filtered by project or title/summary search' and 'offset to page past the cap'. Lacks when-to-avoid or alternatives.

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