Inspect a native API 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 safety profile is covered. The description adds a validation caveat about opaque RenderScript and mentions source URL/version distinctions, which is useful context beyond annotations, but the wording is cryptic and no return format is described.

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 sentences keep it reasonably compact, but the first sentence is front-loaded with the awkward modifier 'Local current reviewed' rather than a clear verb. The second sentence's caveat is relevant but phrased unclearly, so structure is adequate but not polished.

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 inspection tool with no output schema, the description does indicate the returned metadata categories (method, path, body, query) and mentions source URLs/version distinctions. However, it leaves operation-specific meaning and usage context under-specified, which limits completeness.

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?

With only one enum parameter and 0% schema description coverage, the description should explain what each operation value means. It merely notes there are 'eleven documented operations', which matches the enum count but adds no per-value meaning or selection guidance.

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 title and description together make clear that this tool retrieves method/path/body/query metadata for documented operations, rather than executing them. The phrasing 'Local current reviewed' is awkward, but the core purpose is discernible. It does not explicitly distinguish itself from sibling tools that perform the actual operations.

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 offers no guidance on when to use this tool versus the many sibling operations (e.g., create_render, get_template). It states the scope ('eleven documented operations') but never says to call this for inspection before invoking an operation, nor when not to use it.

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