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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false. The description adds meaningful behavioral context beyond this: 'This server never requests your draft and instructs your AI to keep it local—rating sheets and scoring instructions flow to your AI.' This privacy/data-flow detail is not derivable from annotations and is useful for the agent.

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?

Two sentences, no wasted words. The first sentence captures the core action and contents; the second provides a key privacy constraint. Information is front-loaded and every sentence earns its place.

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 load-context tool with one optional parameter and no output schema, the description is complete: it lists the contents loaded, mentions the privacy/behavioral policy, and is easy to understand. It lacks explicit guidance on when to use this versus related tools, but that is covered by dimension 2 and does not undermine overall completeness for this simple action.

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 input schema fully describes the single optional parameter 'detail_level' with enum values and token estimates, so schema coverage is 100%. The description adds no additional parameter information. Baseline 3 is appropriate because the schema does the heavy lifting.

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 'Load' with a clear resource: 'Lenny Zeltser's complete cybersecurity-writing rating toolkit', enumerating 'all 7 sheets, scoring policy, scoring playbook, and cross-references to the writing guidelines.' This distinguishes it from sibling tools like rating_get_sheet (which likely loads a single sheet) and other domain-specific load_context tools.

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 implies when to use this tool—when you need the full toolkit—but does not explicitly state alternatives or exclusions. It does not mention that rating_get_sheet should be used for individual sheets or that this tool is the comprehensive version. No direct comparison to siblings is provided.

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