Fetch a MakeUseOf author profile from a canonical URL to get byline metadata, biography, social links, and recent stories. Returns only the first page.
Get a MakeUseOf author profile. Returns an author's public byline metadata, biography, social links, and recent stories from a canonical author URL. Only the first page is covered.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical MakeUseOf 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 behavioral burden. It does disclose a meaningful trait — the first-page-only pagination limit — and scopes the content as 'public' metadata. But it says nothing about auth/permission needs, rate limits, or whether a non-canonical URL fails.
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 tight sentences, front-loaded with purpose, then return payload, then the pagination caveat. No filler; each sentence contributes distinct 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?
There is no output schema, so the description responsibly enumerates the returned fields and notes the page limit, which is enough for an agent to call it correctly. It could still say more about failure modes for malformed/non-canonical URLs.
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 'url' param is already described as 'Canonical MakeUseOf author URL'. The description's 'from a canonical author URL' merely echoes the schema, adding no format or syntax detail. Baseline 3 when the schema does the heavy lifting.
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 opens with a specific verb+resource ('Get a MakeUseOf author profile') and immediately enumerates what it returns (byline metadata, biography, social links, recent stories). The site-specific scope cleanly separates it from the many other *_author siblings.
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?
It states the required input shape ('from a canonical author URL') and flags the 'Only the first page is covered' constraint, which is useful context. However, it gives no explicit when-to-use/when-not guidance or alternatives, leaving selection implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.