List Khaleej Times section slugs accepted by khaleejtimes_headlines; nested URL paths use hyphens in the slug. Use khaleejtimes_news for the general feed or khaleejtimes_article for one story.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior context beyond annotations: that output slugs are consumed by khaleejtimes_headlines and that nested URL paths use hyphens. It does not discuss result size or caching, so not a full 5.
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?
A single tight sentence front-loads the purpose, then adds format and routing detail with no filler. Every clause earns its place.
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?
An output schema exists, so return values need not be explained. For a zero-parameter enumeration tool with annotations covering safety, the description supplies everything an agent needs to call it and use the results correctly.
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?
Zero parameters, so the baseline is 4. The description still adds value by describing the slug format (hyphenated nested paths) that the returned values follow, which is meaningful for a tool whose output feeds other calls.
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?
States a specific verb ('List') and resource ('Khaleej Times section slugs'), plus the critical detail that these slugs are the values accepted by khaleejtimes_headlines. This clearly distinguishes it from sibling tools that fetch content rather than enumerate section identifiers.
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?
Explicitly routes the agent: this tool for section slugs, khaleejtimes_news for the general feed, khaleejtimes_article for a single story. The condition selecting each alternative is stated, leaving nothing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
