Fetch a Daily Express journalist's public profile by URL, including name, job title, bio, and recent articles. Ideal for media research and content enrichment.
Get a Daily Express journalist profile. Returns one Daily Express journalist's public profile: name, job title, bio, and their recent articles, from a canonical journalist URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Daily Express journalist 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 carries the behavioral disclosure burden. It states the output contents (name, job title, bio, recent articles) and specifies it returns a public profile, implying read-only. It does not mention potential limitations (e.g., truncation of recent articles) or behavior on invalid/non-canonical URLs, which is a moderate gap.
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 a single, efficient sentence with no filler. It front-loads the core action and follows with the return summary, every word earning 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?
For a simple single-parameter read tool with no output schema, the description covers the essential inputs and outputs. It lacks guidance on edge cases like non-existent profiles or URL format validation, but the canonical URL constraint is present in the schema. Overall, adequate for correct invocation.
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 100% (the 'url' parameter is described as 'Canonical Daily Express journalist URL'). The description adds minimal new meaning beyond the schema, but the schema already fully documents the parameter, so baseline 3 applies.
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 verb ('Get') and resource ('Daily Express journalist profile'), and enumerates the returned fields (name, job title, bio, recent articles). It does not explicitly distinguish itself from sibling tools like dailyexpress_article or other author tools, but the resource scope is clear enough.
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: when you need a journalist profile from a canonical URL. However, it does not provide explicit when-to-use/when-not-to-use guidance or name alternatives (e.g., dailyexpress_article for article content). The context is implied but not articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.