Fetch a Khaleej Times author profile by submitting a canonical author URL. Returns the author's name, photo, biography, and first-page recent articles.
Get a Khaleej Times author profile. Returns a Khaleej Times author's name, photo, biography, and most recent articles (first page) from a canonical author profile URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Khaleej Times author URL |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the full burden. It discloses the output fields and the requirement for a canonical URL, but does not mention potential failure modes, authentication, rate limits, or whether the operation is read-only. Adequate but not comprehensive.
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 sentence that front-loads the action and immediately specifies the expected output. No fluff or repetition; every word contributes to understanding what the tool does.
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?
For a simple one-parameter tool with no output schema, the description adequately covers the purpose, input, and return fields. It notes that articles are the 'most recent' and 'first page', giving a sense of pagination. However, it omits details like error conditions or whether a non-canonical URL is accepted, but these are minor.
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 100%, so the URL parameter is documented. The description adds the requirement that the URL be 'canonical', providing extra semantic clarity beyond the schema's generic 'Canonical Khaleej Times author URL' description, which is redundant but reinforces the field.
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 action ('Get a Khaleej Times author profile') and specifies the resource and return content (name, photo, biography, articles). It distinguishes itself from siblings like khaleejtimes_article and other publication author tools by scoping to Khaleej Times author profiles.
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?
The description implies usage for author profiles but does not explicitly mention when not to use it or alternatives. It lacks exclusions like 'for articles, use khaleejtimes_article' or reference to other author tools. The context is clear enough, but no direct guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.