cbc_author

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

With no annotations provided, the description carries the behavioral disclosure burden. It does state that the tool 'Returns one CBC journalist's public profile' and lists the output fields, which is useful. However, it does not disclose error behavior, whether at least one parameter is required, or any rate-limit/auth considerations, leaving some behavioral ambiguity.

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, front-loaded sentence that states the action and the return payload without any filler. Every clause adds useful information, and it is appropriately sized for a simple lookup tool.

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?

The description covers the return fields well, but with no annotations and no output schema, it leaves gaps: it does not state that url or slug is needed, what happens if neither is provided, or how many 'most recent articles' are returned. These are meaningful omissions for an agent deciding how to invoke the 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 description coverage is 100%, so the baseline is 3. The description does not add parameter-specific meaning beyond the schema; it does not clarify that url and slug are alternatives or that at least one should be supplied, but the schema already documents both parameters well.

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 a CBC journalist profile.' It further enumerates the returned fields (name, job title, biography, photo, profile links, recent articles), making the tool's purpose unmistakable and distinguishing it from article/news/section tools like cbc_article and cbc_headlines.

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 clearly implies when to use this tool: whenever a CBC journalist's public profile is needed. It does not explicitly name alternatives or exclusions, but the context is clear enough that an agent would not confuse it with article retrieval or other author tools.

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