Inspect a current native operation

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real value beyond them by declaring that the lookup is local and requires no credentials and issues no provider request, and that the returned schema is 'reviewed' with provenance.

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 compact sentences with no filler, and the payload description is front-loaded. The first sentence is a dense noun phrase rather than a full clause and the second is clipped, which costs a little readability without wasting space.

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?

For a one-parameter introspection tool with no output schema and no nested objects, the description adequately sketches what comes back (method, path, query, body schema and provenance). It would be stronger if it indicated the return format or how the schema should be consumed.

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 100% and the single 'operation' parameter already carries an enum and a description, so the schema does the heavy lifting. The description only reinforces that the value is a 'native tool' name, adding no format or selection guidance beyond the enum.

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 states a specific verb (inspect/get) and resource (the reviewed method/path/query/body schema plus provenance for a single named native operation), which is clearly distinct from the sibling tools that actually perform those operations. It stops short of explicitly contrasting itself with those siblings, but the 'one native tool' scoping makes the target unambiguous.

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?

Usage is only implied: 'No credentials or provider request' hints that this is a safe introspection step rather than an actual provider call, but there is no explicit 'use this before invoking X' instruction or named alternative. An agent can infer the intent, yet nothing states when this tool should be preferred.

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