Fetch a public Android Police author profile from a canonical URL. Get byline metadata, biography, social links, and recent articles from the first page.
Get an Android Police author profile. Returns a public author's byline metadata, biography, social links, and recent articles from a canonical author URL. Only the first page is covered.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Android Police author URL |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does reasonably well: it discloses the returned content (byline metadata, biography, social links, recent articles), signals the data is public (no auth implied), and explicitly warns 'Only the first page is covered' – a genuinely useful pagination-scope disclosure.
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?
Three tightly-packed sentences with purpose front-loaded first, return contents second, and the pagination caveat last. No filler sentences.
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?
No output schema and no annotations, so the description must cover both behavior and returns – it does explain the return payload and the first-page limit. The only gap is the absence of any alternative-tool routing guidance, which for a simple single-URL fetch is a minor omission.
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?
One required parameter at 100% schema coverage sets the baseline at 3. The description repeats 'canonical author URL' but adds no format guidance, examples, or lookup hints beyond what the schema already declares.
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 ('Get') and resource ('Android Police author profile'), distinguishing it from siblings like androidpolice_article, androidpolice_news, and androidpolice_sections. An agent can immediately tell this returns a profile rather than content.
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 rather than stated: 'from a canonical author URL' hints that a URL is required, but there is no explicit when-to-use, when-not-to-use, or mention of an alternative (e.g., using androidpolice_article for individual pieces). Adequate but with a clear gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.