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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real semantic value the annotations do not: the matrix describes what is *actually installed* versus declared, and it defines declared_only as 'a schema without an executable witness', which tells the agent how to interpret unconfirmed entries.

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 filler, with the content inventory front-loaded and the glossary notion of declared_only appended as a clarifying second sentence. Dense but every clause adds information.

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 input params and no output schema, the description carries the burden of explaining what comes back, and it does so by enumerating the matrix's sections and defining its key status term. Missing only guidance on when in a workflow to call it relative to sibling inspection tools.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies a parameterless snapshot by framing the output as a machine-readable matrix rather than a filtered report.

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 names a specific resource and enumerates its contents (installed Lens producers, replay/projection controls, profiles, limits, contract tests), so the agent knows this is an introspection/capabilities-matrix tool rather than a query tool. It does not differentiate itself from siblings such as law_inspect, law_packages or law_rules, which also sound like introspection endpoints.

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?

There is no statement of when to call this tool, no prerequisites, and no mention of any alternative. The agent must infer from the name and content list that this is the discovery endpoint to use before other Lens calls.

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