BedrockNews metadata: what the site is, how the GRIN/CLAIMS/NOVEL frameworks work, terms of use + attribution, and every machine-readable surface. Also returns the full capability map (every tool, prompt, and resource) — call this first.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description aligns perfectly. It adds significant value by specifying exactly what the tool returns: site metadata, framework explanations, terms of use, and a capability map. There is no contradiction.
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 a single sentence that packs essential information: what the tool does, what it returns, and when to call it. It is front-loaded with the key purpose and is concise with no wasted words.
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 no parameters and no output schema, the description fully informs the agent about the tool's purpose and return content. It covers the key aspects: what metadata is returned and the instruction to call it first. Completeness is high for a simple discovery tool.
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 tool has zero parameters, so per guidelines the baseline is 4. The description does not need to add parameter information. It correctly describes the output without referencing parameters.
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 that the tool returns 'BedrockNews metadata' and 'the full capability map (every tool, prompt, and resource)'. It distinguishes itself from sibling tools like get_article and list_categories by focusing on overarching site info rather than specific articles or lists.
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 'call this first', providing a clear usage directive. While it does not explicitly state when not to use it or list alternatives, the instruction to use it first is strong guidance for an agent.
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.
Each tool serves a distinct purpose: retrieving articles, graphs, related stories, site info, categories, and listing stories. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern (get_*, list_*), making the API predictable and easy to navigate.
With 6 tools, the server is well-scoped for a specialized news analysis API. Not too few, not too many.
Covers core functionality (listing, retrieving, related stories, metadata). Minor gap: no full-text search, but title search suffices for many use cases.
