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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the description only needs to add context beyond that. It adds a useful privacy/behavioral note about not requesting program docs and keeping data local, but it also makes a misleading structural claim (8 rows versus 10 asset enum values), which weakens transparency.

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 compact and front-loaded with the core purpose. The second sentence about server behavior and local analysis is somewhat tangential but conveys a relevant data-handling constraint; the main content stays reasonably tight.

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 no output schema, the description must accurately describe the returned structure, but the '8 AI-specific asset rows' statement contradicts the 10-value asset enum. The schema rescues parameter details, but the mismatch leaves the description incomplete and potentially misleading about what the tool will return.

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% and every parameter has enums and descriptions, so the baseline is 3. The description adds some meaningful context by tying asset and function to the matrix's row/column structure, but it does not substantially explain parameters beyond what the schema already provides.

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 verb-resource pair is clear: it returns a structured AI Defense Matrix organized by asset rows and NIST CSF function columns. However, it claims '8 AI-specific asset rows' while the input schema defines 10 asset enum values, so the description is not fully accurate.

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 use when the AI Defense Matrix is needed and mentions optional filtering by asset or function, but it gives no explicit when-to-use guidance, no exclusions, and does not point to alternatives such as aidefense_cross_map or aidefense_get_framework_alignment.

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