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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds meaningful behavioral context beyond those: it discloses that the server never requests vulnerability notes and instructs the AI to keep them local, and it explains the optional sibling blocks. This goes well beyond the annotation baseline.

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-loads the core purpose, and contains no fluff. Every sentence adds substantive information, including usage and privacy behavior.

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?

Given the tool's simplicity (one optional boolean parameter, no output schema, strong annotations), the description covers purpose, parameter behavior, and data handling. It does not detail the exact return structure, but the parameter description in the schema partially covers that, and the absence of an output schema makes some lack of return detail acceptable.

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% with a clear parameter description, so baseline is 3. The tool description adds value by explaining what sibling frames are (adjacent frameworks that aren't the structural backbone) and providing an explicit usage example ('Pass include_siblings: false'), enriching the schema's semantics.

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 ('Get') and a specific resource ('Lenny Zeltser's Vuln frameworks'), and distinguishes primary frameworks from optional sibling frames. It clearly conveys that this tool retrieves the frameworks that structurally underpin a brief, differentiating it from sibling get_frameworks tools for other domains.

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 provides clear context for when to use the tool (to obtain the structural frameworks and optionally adjacent sibling frames) but does not explicitly name alternatives or state when not to use it. It does, however, give a direct usage hint about the include_siblings parameter, which adds practical guidance.

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