ctvnews_article

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

With no annotations provided, the description carries the full burden. It mentions that the tool returns public metadata and body paragraphs, which is useful, but it does not disclose any potential errors, rate limits, or response format quirks. For a simple read operation, this is acceptable but not rich; it adds some behavioral context but lacks depth.

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, front-loaded with the purpose, and includes essential details like the URL format and exclusions without unnecessary fluff. It is well-structured and concise.

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?

With no output schema, the description explains that it returns metadata and body paragraphs, giving the agent an idea of the response. It also specifies the URL format. It could mention more about the response structure or error cases, but for a simple article fetch tool, it is adequately 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 schema describes the url parameter as 'Canonical CTV News article URL', and the description adds the specific URL pattern (https://www.ctvnews.ca/<section>/article/<slug>/) and what counts as an article page, providing additional semantics beyond the schema. Since schema coverage is 100%, the description enhances the parameter meaning.

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 retrieves CTV News article content, specifies the resource (CTV News article) and the action (Get), and includes a URL pattern. It also explicitly excludes video, photo-gallery, and live-stream pages, distinguishing it from other article tools and clarifying its scope.

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 usage for CTV News article URLs and explicitly states that video, photo-gallery, and live-stream pages are not article pages, providing an exclusion. However, it does not name alternative tools or provide broader when-to-use guidance relative to other publication article tools, so it falls short of a 5.

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