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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), and the description is consistent with that. It adds real value by disclosing what the response contains: the union of available tools, their safety classifications, and their input schemas. It stops short of noting pagination or scoping limits, which is minor for a discovery call.

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, front-loaded with the purpose and followed by the return contents and the usage cue. No redundancy or filler.

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 reasonably covers the return shape (tool list, safety classes, schemas) and the rationale for calling it. For a single-parameter read tool with annotations handling the safety profile, nothing essential is missing.

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?

One parameter with 100% schema description coverage, so the schema carries the load. The description adds only a framing note that the manifest is keyed to a kernel's device type, which slightly clarifies what kernelId selects but adds no format or constraint detail.

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?

Names a specific verb ('Get') and resource ('tool manifest'), scopes it ('for a kernel's device type'), and states exactly what the payload contains (tool list, safety classification, input schemas). This distinguishes it from relay/execution siblings like pcc_relay_tool_call, which invoke tools rather than enumerate them.

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?

Explicitly states when to use it: 'Use to understand what tools are available before making tool calls.' This gives clear context but names no alternative (e.g., a per-tool lookup or pcc_get_tool_result) and sets no exclusions.

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