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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, and the output schema carries the return shape, so the bar is lower. The description adds the meaningful trait 'deterministic' and the disclaimer field, but says nothing about cost, latency, or that results are stable across calls beyond that word.

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?

A single front-loaded sentence with no filler. It is slightly list-like ('pricing, composition, and the professional-review disclaimer') but every item corresponds to a real return field, so nothing is wasted.

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 an output schema that fully specifies returns, rich annotations, and no inputs, the description covers enough to call the tool correctly. It does not need to enumerate return values further.

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?

Zero parameters, so baseline applies; nothing is mistyped or misleading. The description doesn't need to explain any inputs.

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?

States a specific verb and resource ('Return deterministic capabilities, version, pack digest, pricing, composition...') for the agent descriptor. An agent can tell this reports static metadata about itself rather than performing a compile/get/verify action. It doesn't explicitly contrast with siblings, but the resource scope is self-evident.

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?

No statement of when to call this versus compile_disclosure, get_framework, or verify_result. The reader must infer that this is the 'inspect current agent' call. No prerequisites or exclusions are given.

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