nbc_article

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the behavioral burden. It usefully discloses that only public content is returned and that access controls are not bypassed, and it names the output categories. It does not address error behavior, invalid/non-canonical URLs, or the structure/format of the returned metadata, leaving some behavioral gaps.

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 short sentences, front-loaded with the action and output, with the important access-control caveat at the end. No filler or repetition of schema-only details.

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 one-parameter read tool with no output schema, the description covers what the tool takes (canonical URL), what it returns (metadata and body paragraphs), and its limits (public only, no access-control bypass). It could add return-structure detail, but nothing essential is missing for invocation.

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 sole 'url' parameter is already fully described in the schema as a canonical www.nbcnews.com article URL, so schema coverage is 100%. The description reinforces 'canonical article URL' and the public-access constraint but adds no new param meaning beyond the schema.

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 uses a specific verb and resource: 'Get NBC News article content' and tells the agent exactly what is returned (metadata and body paragraphs) from a canonical article URL. It stops short of explicitly distinguishing itself from sibling NBC tools like nbc_headlines or nbc_news, though the URL-scoped language makes the distinction mostly implicit.

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 implies the tool is for fetching full article content from a canonical www.nbcnews.com URL and implies it should not be used for access-controlled content ('does not bypass login...'). However, it does not name alternatives or state when to prefer a sibling tool, so usage guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.