knowledge_topics

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the tool takes no parameters and 'reflects the live published corpus,' which implies real-time consistency. No contradiction with annotations.

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 three sentences, front-loaded with the action and scope, followed by usage guidance and an explicit alternative. Every sentence contributes value: what it lists, when to use, and a contrast with knowledge_search. No redundancy or filler.

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 zero-parameter tool, the description covers the purpose, output content (categories, tags, counts, url, total), usage context, and an explicit alternative tool. An output schema exists, so return values need not be spelled out. The description is sufficiently complete for an agent to select and invoke it correctly.

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 tool has zero parameters, and the schema coverage is 100% (empty properties object). The description explicitly says 'It takes no parameters,' which confirms the absence of any inputs. Baseline for 0 params is 4, and the description adds no further parameter explanation needed.

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 the specific verb 'Lists' and names the resource ('FoundRole's published career-guidance blog') with concrete deliverables (categories, tags, counts, url, total count). It distinguishes from sibling tool knowledge_search by explicitly stating what it does not do ('does not retrieve articles for a specific question; knowledge_search does that').

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 states when to use this tool ('factual source for questions about the blog's topics or overall coverage') and provides an explicit exclusion with the alternative ('It does not retrieve articles for a specific question; knowledge_search does that'). This gives clear guidance on choosing between sibling tools.

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