list_news

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

With no annotations provided, the description must convey all behavioral traits. It fails to mention that the tool supports pagination (limit/offset), the format of the return value, or any side effects. This lack of transparency leaves agents guessing about behavior.

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 one-sentence description is too terse, omitting essential details like pagination and parameter semantics. While concise, it sacrifices clarity and usefulness, making it hard for an agent to leverage the tool effectively.

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?

Given 4 parameters, no output schema, and no annotations, the description should provide more context about the return structure, filtering behavior, and pagination. The current description is insufficient for an agent to use the tool without additional guesses or errors.

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 coverage is 0%, so the description must explain parameters. It mentions 'project' and 'search' filters but does not explain 'limit' and 'offset' meaning or default values. For 4 parameters, only partial guidance is given, insufficient for an agent to use parameters correctly.

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 news entries, with optional filtering by project or search. It distinguishes from 'get_news' (singular) which likely retrieves a single news entry. However, it does not mention pagination via limit/offset, which is implied by the schema.

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?

No explicit when-to-use or alternatives are mentioned. The description only hints at filtering use cases but does not contrast with 'get_news' or other list tools. An agent would need to infer appropriate usage from context.

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