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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, but the description adds significant behavioral context: the profile parameter annotates rather than filters, every section is returned for cross-profile comparisons, and the server never requests or retains the user's assessment notes. This privacy-local analysis disclosure goes well beyond structured 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, dense but well-structured: purpose and payload, framework list, then key behavioral clarifications. The framework enumeration is lengthy but useful, and the privacy statement earns its place. Nothing is redundant with the schema.

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?

No output schema exists, so the description carries the burden of explaining the return value, which it does thoroughly by listing the payload components. It also covers the key behavioral nuance (no filtering) and the data-handling guarantee, making it complete for a loading tool of this complexity.

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%, so each parameter already has a description. The description adds valuable context by explaining the payload structure and explicitly reinforcing that the profile parameter annotates rather than filters, with the rationale of enabling cross-profile comparisons. It also mentions the mcpHandoffs array, giving context for how parameters affect the response, even though this is not parameter-specific.

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 it loads Lenny Zeltser's security assessment report writing context for local analysis, enumerates the payload components, and distinguishes itself from sibling get_* tools by emphasizing full-context loading rather than filtered retrieval. The specific verb 'Load' and the resource scope make the purpose unambiguous.

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 explicitly frames the tool as for local analysis and states the server never requests assessment notes, implying it is not for server-side review or scoring tools like assessment_review_report. It also explains the profile parameter's annotate-not-filter behavior, setting expectations for when to use this full-context loader. However, it does not explicitly name an alternative tool for narrower needs.

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