Fetch an Indian Express author's profile, including byline metadata, biography, and recent articles, using the canonical author URL.
Get a The Indian Express author profile. Returns a The Indian Express author's byline metadata, biography, and recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical The Indian Express 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 present, so the description carries the disclosure burden. It clearly states the returned data (byline metadata, biography, recent articles), but does not mention error behavior, potential pagination, or absence of side effects. For a simple read operation this is adequate but not thorough.
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?
Two sentences with no filler: the first front-loads the action, the second details the return payload. Every sentence earns its place and the tool name is not unnecessarily repeated.
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 one-parameter read tool with no output schema, the description covers the essential purpose and return values. It omits minor details like ordering or limits of 'recent articles,' but nothing critical for a correct call.
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% and the single parameter 'url' is already described as a canonical author URL. The description only repeats 'canonical author URL' without adding format or usage details, so it provides no extra meaning beyond the schema.
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 states a specific action and resource: 'Get a The Indian Express author profile' and enumerates returned content (byline metadata, biography, recent articles). It is clearly distinct from sibling tools for other publications and from indianexpress_article, though it doesn't explicitly name 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?
Usage is implied: given a canonical author URL, fetch the profile. The description does not provide when-not-to-use guidance, alternatives, or how to discover the canonical URL, so it leaves the agent to infer the trigger condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.