createNews

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

No annotations are provided, and the description does not disclose any behavioral traits. For a mutation tool, details like whether it returns the created object, idempotency, permission requirements, or side effects are entirely missing.

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 description is extremely concise (two words), but it is under-specified to the point of being uninformative. Conciseness should not sacrifice essential information; here, it fails to earn its place by providing minimal value.

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 complexity of the input schema (nested objects, multiple required fields) and the absence of an output schema or annotations, the description is grossly incomplete. It does not explain what the tool returns, which fields are mandatory, or how to handle 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?

The schema has 0% description coverage, and the description 'Create news' adds no meaning to the parameters. The input schema includes complex nested objects (pathParams, bodyParams) with no explanation of their format or role, leaving the agent to infer entirely from names and structure.

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 'Create news' clearly indicates the verb (create) and the resource (news). It is a straightforward purpose, but it does not elaborate beyond the name, missing opportunity to specify what kind of news (e.g., article, announcement) or distinguish from siblings like 'updateNews'.

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 alternatives. There are sibling tools for updating, deleting, and listing news, but the description gives no context about when to create vs. use other operations, nor any prerequisites or constraints.

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