getNewsListByProject

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

No annotations exist, so the description must convey behavior. While 'List' implies a read operation, it does not disclose pagination, format selection, or other behavioral traits evident in the schema (e.g., offset, limit, format). The description is too minimal to alert the agent to these details.

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 4 words, the description is too brief to cover the tool's capabilities. While concise writing is valued, this under-specifies the tool's input parameters and behavior, making it unhelpful.

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 the tool's complexity (5 parameters, nested objects, format enum, pagination), no output schema, and no annotations, the description is severely incomplete. It fails to address pagination, format, or the required path parameters, leaving the agent largely uninformed.

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%, so the description must add meaning. It only hints at 'by project' (mapping to projectId) but provides no explanation for format, offset, limit, or nometa. Key parameters remain unexplained.

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 by project' clearly states the action (list) and the resource (news), and the 'by project' qualifier suggests filtering by project, which differentiates it from sibling tools like getNewsList that list all news. However, it does not explicitly differentiate from alternatives.

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 guidance is provided on when to use this tool versus siblings such as getNewsList (all news) or getNews (single news). The description simply states what the tool does without context for selection.

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