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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds genuinely new behavioral facts: it is metadata only, no invocation occurs, and the response reports whether encrypted invocation preparation, read-only execution, and a consumer pilot session are required. That is useful pre-flight information beyond the structured fields.

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 body is dense and front-loads the key capability statement, but the leading 'Private draft:' label is unexplained and could be misread as referring to a draft contract or a draft-stage tool. Otherwise it is appropriately sized for the amount of behavioral detail conveyed.

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 the return-value hints are a bonus rather than a requirement. However, for a two-required-parameter lookup with zero schema coverage, leaving both parameters uncharacterized is a meaningful completeness gap.

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 description coverage is 0% for two required parameters (projectId, operationId), so the description must carry the burden — but it never mentions either parameter. It doesn't clarify that operationId must refer to an already-approved contract or how projectId scopes the lookup.

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 core sentence names a specific verb ('inspect') and a scoped resource ('one selected and approved provider operation contract'), which distinguishes it from the plural list/search siblings and from get_provider_invocation. The 'Private draft:' prefix is unexplained noise that slightly muddies an otherwise precise statement.

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?

It states the preconditions for a successful call — the operation must be selected and approved, and the account must own it or hold an active grant — which is real routing context. It does not explicitly contrast with search_provider_operations or get_provider_invocation, so the when/when-not framing is implicit rather than stated.

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