Get a Gizmodo author's name, job title, biography, headshot, social links, and recent articles from a canonical author URL. Provides structured JSON data.
Get a Gizmodo author profile. Returns a Gizmodo author's name, job title, biography, headshot, social links, and most recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Gizmodo 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 present, the description is responsible for behavioral disclosure. It only lists what the tool returns (output fields) and does not mention any side effects, authentication requirements, rate limits, or failure conditions. Minimal disclosure beyond the schema.
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 two concise sentences: the first states the purpose, the second lists the return fields. No waste, front-loaded, and effective.
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?
Given the tool is a simple lookup with a single parameter and no output schema, the description adequately conveys what the agent will receive (name, title, bio, headshot, social links, recent articles). It could specify the number of recent articles or format, but for a basic profile fetch it is sufficiently complete.
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 input schema already provides a complete description of the 'url' parameter ('Canonical Gizmodo author URL') at 100% coverage. The description repeats this without adding additional meaning, so it meets the baseline of 3 without exceeding it.
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 clearly states the verb 'Get' and the resource 'Gizmodo author profile', and enumerates the returned fields (name, job title, biography, etc.). It is unambiguous about the publication (Gizmodo) but does not explicitly differentiate from sibling author tools like nzherald_author, though the branding makes the distinction obvious.
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?
There is no guidance on when to use this tool versus alternatives or any stated exclusions. The description implies usage but does not provide any context about when it is appropriate or not, leaving the agent to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.