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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it explicitly states that this server never requests sample data/indicators and instructs the AI to keep materials local, which is valuable privacy-relevant behavior.

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 well-structured sentences, front-loaded with the primary purpose, followed by a compact enumeration of content areas and a privacy note. Every phrase adds relevant information, with 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?

With zero required parameters and no output schema, the description should explain what the tool returns. It does this reasonably by stating it 'surfaces' review criteria and mentions the flow of guidelines and template for local analysis. It could be slightly more explicit about output format, but for selection and invocation the core information is present.

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% and the parameter descriptions already list allowed enum values. The description adds value by naming review themes (identification, capabilities, indicators, evidence, ecosystem, detection) and mentioning cross-cutting criteria and anti-patterns, giving the agent semantic context for choosing focus and section parameters.

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 specific verb and resource: 'Get Lenny Zeltser's expert criteria for reviewing an existing malware analysis report.' It further enumerates concrete content themes (identification, capabilities, indicators, evidence, etc.), which clearly differentiates this tool from sibling tools like malware_get_template or malware_get_guidelines.

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: when reviewing an existing malware analysis report. It gives no explicit exclusions or alternatives, but the stated purpose and the 'never requests your sample' privacy note provide practical context for appropriate invocation.

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