Retrieve an author's public profile and recent story cards from a canonical Houston Chronicle author URL.
Get a Houston Chronicle author profile. Returns an author's public profile and recent story cards from a canonical Houston Chronicle author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Houston Chronicle author URL |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that a profile plus recent story cards are returned, which tells the agent the shape of the response, but says nothing about auth, rate limits, or failure behavior for an invalid URL. Adequate but not rich.
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?
Two short sentences, front-loaded with the action and followed by the return shape. No filler, every clause earns 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 single-URL read tool with no output schema, the description successfully conveys both the operation and the returned payload, which is the key missing structured information. It lacks only edge-case behavior that a richer definition could add.
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?
Only one parameter with 100% schema description coverage, so the schema already documents 'url'. The description restates 'canonical Houston Chronicle author URL', reinforcing format expectations but adding no syntax detail beyond the schema. 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?
States a specific verb and resource ('Get a Houston Chronicle author profile') and further specifies the return content ('public profile and recent story cards'). It is clearly distinct from siblings like houston_chronicle_article or houston_chronicle_news, though it never names an alternative explicitly.
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 phrase 'from a canonical Houston Chronicle author URL' implies the required input context, but there is no explicit when-to-use guidance or comparison against houston_chronicle_article/headlines. Usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.