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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral boundary not in the annotations: it does not trigger the Survival Audit checkout, and it returns live rather than verdict data. That said, it stops short of describing scope, freshness guarantees, or limits.

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?

Three terse, front-loaded sentences with no filler; the key qualifier ('Live inspect tool') comes early. It is efficient, though the first sentence is a bare restatement of the tool name and adds little.

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?

An output schema exists, so return values need not be explained, and a zero-parameter read-only inspect tool has a low bar. Still, the description never says what the contract contains or when an agent should reach for it over related contract/export tools, leaving meaningful context gaps.

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 and the schema has 100% description coverage, so there are no parameter semantics to explain. The baseline for a no-parameter tool applies; the description correctly does not pad with irrelevant argument 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?

The name states the resource (Pine converter contract) and the description adds 'Live inspect tool' plus 'not a verdict', which characterizes the operation type. However, it never states in plain terms what the tool returns or does, and it does not distinguish itself from siblings like get_product_contract or inspect_pine_export_capability. The purpose is legible but vague.

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 tells the agent what this is not ('not a verdict', 'does not start Survival Audit checkout') but gives no positive when-to-use condition and names no alternative tool. The exclusions are useful boundary markers but fall short of routing guidance.

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