Inspect a current native operation

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is low. The description adds genuine context beyond them: it is a purely local lookup requiring no credentials and it returns 'pinned provenance,' disclosing that schema versions are anchored. That is useful extra behavioral context.

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 dense sentences with no filler, and the core deliverable (method/path/query/body schema) is front-loaded. Occasionally cryptic jargon like 'pinned provenance' costs a little readability, but the structure is efficient.

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?

No output schema exists, so the description carries more of the return-value burden. It names the returned components (method/path/query/body schema and provenance) but does not sketch their shape or structure for a meta-tool spanning dozens of operations, leaving a modest 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 100%, and the single 'operation' enum is fully documented in the schema itself, so the baseline is 3. The description adds only a general sense of what the parameter selects ('one selected native tool') without elaborating on enum semantics beyond the schema.

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: it returns the local method/path/query/body schema and pinned provenance for one selected native tool. This implicitly distinguishes it from the sibling native tools, which actually invoke providers, but it never names a sibling explicitly. Clear and specific without relying on the title.

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 phrase 'No provider call or credentials' implies this is a safe inspection path used before invoking a native tool, but the description never states when to choose it over just calling the native operation. Usage is left to inference rather than explicit when/when-not guidance.

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