Fetch The Hill author details from a canonical URL via Crawlora MCP, including byline metadata, biography, and recent articles.
Get a The Hill author profile. Returns a The Hill author's byline metadata, biography, and recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical The Hill author URL |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral disclosure; it does indicate this is a retrieval operation and states the returned content (byline, bio, recent articles) plus the canonical-URL requirement. It does not disclose possible errors, non-canonical URL behavior, or response shape, but for a simple read-only profile call the core behavior is clear.
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?
One sentence with no filler; the purpose is front-loaded, and the return fields are given in a compact list. Every clause adds useful information.
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 single-parameter, no-output-schema tool, the description covers the input requirement and the high-level return data, which is enough for an agent to select and call it. It could still add a canonical URL example or note about article count, but that is a minor gap for this low-complexity tool.
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 already documents the only parameter at 100% coverage as 'Canonical The Hill author URL'; the description merely repeats the canonical-URL idea and adds no format, examples, or derivation instructions. Baseline 3 applies because the schema carries the parameter documentation.
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 opening verb 'Get' plus the resource 'The Hill author profile' identifies exactly the operation, and the second sentence enumerates returned fields (byline metadata, biography, recent articles), making it distinct from sibling tools like thehill_article and thehill_sections. No ambiguity about what this tool does.
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 the tool is appropriate when an agent needs an author's bio, metadata, or recent articles, and it names the canonical URL as the input context. It does not explicitly say when not to use it or point to alternatives such as thehill_article or thehill_headlines, so the guidance is inferred rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.