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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the content scope ('public' metadata plus body paragraphs) and says nothing about auth, rate limits, or partial-article behavior. Some added value, but modest against the annotation coverage.

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 tight sentences with zero waste, common to this family of siblings. The primary action (fetch) is front-loaded before the routing hint.

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 an output schema present, return values need no explanation. The description covers purpose, input, and routing, and is complete for a simple single-parameter fetch tool; only richer retrieval behavior (pagination, partial content) is absent.

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?

Schema coverage is 100% and the sole 'url' parameter is described as 'Canonical Raw Story article URL'. The description's 'canonical `url`' phrasing merely mirrors the schema rather than adding format or syntax guidance, so baseline 3 is appropriate.

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 (Fetch) and resource (Raw Story article metadata and body paragraphs) with a precise scope, and names the sibling tools it is not (rawstory_headlines, rawstory_news). An agent can distinguish it from the other rawstory tools without opening any schema.

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?

Explicitly routes the agent to rawstory_headlines for finding stories and rawstory_news for the general feed, which implies this tool is used once a canonical URL is known. Clear context, but no explicit statement of when this tool itself is the right choice versus, e.g., a search.

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