cbsnews_author

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

No annotations are provided, so the description carries the full disclosure burden. It notes that the profile is a public team-page profile and handles the 'headshot (when the page has one)' optionality, but it does not explicitly state read-only behavior, error behavior, or whether 'recent articles' are limited or paginated. For a simple retrieval tool this is acceptable but not rich.

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 with the primary action front-loaded, followed by a compact list of returned fields. There is no filler, no repetition of schema information, and every clause contributes useful detail.

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 one-parameter read tool with no output schema, the description covers the input via the schema and the output surface via the list of returned fields, including the optional headshot. Minor gaps such as the recency limit of 'recent articles' and error behavior are not critical for this 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?

Schema coverage is 100%, and the url parameter is already described as a 'Canonical cbsnews.com/team/<slug> author URL', so the schema fully documents the parameter. The tool description adds general context about returning a team-page profile but does not need to repeat the parameter details.

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 opens with a clear verb-resource pair ('Get a CBS News author profile') and enumerates the exact contents: name, biography, coverage topics, headshot, social links, and recent articles. This is unambiguous and distinguishes the tool from cbsnews_article, cbsnews_headlines, and other outlets' author tools.

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 'Returns one CBS News author' phrasing implies this is for a single specific author profile, but the description gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives such as cbsnews_news or cbsnews_sections. It is adequate but leaves the agent to infer usage from the pattern alone.

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