nemesis_explain

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description adds value by explaining the explanatory purpose and the topic list. It does not contradict annotations and provides contextual framing beyond the structured data.

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 reasonably short, but it repeats the topic list twice (once in parentheses and once after 'Topics:'), which is redundant. The core guidance is useful, but the duplication detracts from conciseness.

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 simple read-only explanation tool with one parameter and no output schema, the description covers the tool's purpose, usage context, and accepted topics. It lacks explicit statement about whether only the listed topics are allowed, but this is a minor ambiguity for a low-complexity 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?

The schema covers the 'topic' parameter with examples, but the description adds the full list of topics (including edge and privacy) and clarifies that the parameter should be one of these security topics, enhancing the schema's example-based definition.

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 explains how Nemesis Shield covers a security topic, lists the specific topics, and distinguishes it from action-oriented sibling tools like nemesis_protect and nemesis_scan.

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?

It provides explicit usage guidance—'Use it to answer "why" or "what does it stop"'—which clarifies when to invoke it. However, it doesn't mention when not to use it or explicitly compare to alternatives.

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