getNewsList

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

There are no annotations to provide safety or side-effect hints, and the description offers no behavioral details. It fails to disclose pagination behavior (limit/offset), the required format path parameter, or the return format, leaving the agent entirely in the dark.

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?

At two words, the description is under-specified rather than concise. It lacks necessary details to be useful, and while it is short, it does not earn its place because it conveys no meaningful invocation guidance.

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?

With no annotations, no output schema, required nested path parameters, and no parameter descriptions, the description 'List news' is far from complete. An agent cannot determine required inputs, expected outputs, or behavioral nuances from this minimal text.

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 0% and the description does not mention any of the parameters. The required `format` enum and the optional `limit`, `nometa`, and `offset` query parameters are completely unexplained, providing no semantic guidance beyond the bare schema names.

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 'List news' identifies the action and resource, but it is vague about scope—whether it lists all news or news filtered by project. It does not distinguish getNewsList from sibling tools like getNewsListByProject, making it ambiguous for an agent to select the correct one.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives such as getNewsListByProject or getNews, nor does it suggest any exclusions or preferred contexts.

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