featured_workUse this when someone asks for Cameron Wilson's best, signature, representative, or recommended journalism. Return the pieces he would point a new reader to first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| items | Yes | ||
| title | No | ||
| description | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds meaningful context by explaining the curation behavior—'the pieces he would point a new reader to first'—which goes beyond a trivial read operation. It does not disclose edge cases or response details, but the additional curation rationale warrants a 4.
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 sentences long, front-loaded with the usage trigger, and contains no fluff or redundant information. Every word contributes to understanding the tool's purpose and behavior.
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 simple tool with one optional parameter, annotations covering safety, and an output schema (though not shown), the description is largely complete. It clearly explains the tool's purpose and selection criteria. The only notable omission is how the 'limit' parameter behaves, but that is a minor gap given the tool's simplicity and the schema's constraints.
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 has one parameter 'limit' with no description (schema coverage 0%). The description does not mention 'limit' at all, failing to compensate for the lack of schema documentation. While the parameter's name, type, default, and constraints are somewhat self-explanatory, the description should clarify that 'limit' controls the number of returned pieces, so it earns only 2.
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 tool returns Cameron Wilson's best, signature, representative, or recommended journalism. It uses a specific verb ('return') and identifies the exact resource and selection criteria, distinguishing it from siblings like 'latest_work' or 'recommended_reading' by focusing on his personal curation for new readers.
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 explicitly says 'Use this when someone asks for Cameron Wilson's best, signature, representative, or recommended journalism,' which is a clear trigger condition. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5 but is stronger than a 3 because the use case is well-defined.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools overlap in purpose: search vs. search_journalism both search but differ in advanced filters; fetch vs. get_item both retrieve by ID but with different output types; featured_work vs. recommended_reading both return curated lists. The descriptions help somewhat but boundaries remain unclear for an agent.
Tool names mix styles: bare verbs (fetch, search), verb_noun (get_item, search_journalism), and descriptive phrases (featured_work, latest_work, recommended_reading, work_by_topic). No consistent pattern across all names.
With 8 tools covering search, retrieval, and curated lists, the count is well-scoped for a specialized journalism archive. Each tool serves a distinct niche, and the number is within the ideal 3-15 range.
The surface covers the major workflows: general search, advanced search, item retrieval, and curated/featured lists. Minor gaps like bulk listing or topic enumeration without search exist but are addressable via search_journalism.