transform.inspect

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

No annotations exist, so the description must disclose behavioral traits. It does not state whether the tool is read-only or destructive, what side effects occur, or what the output is. The word 'process' may imply mutation, but 'inspect' suggests read-only, creating ambiguity.

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 description is a single sentence of 8 words, which is too short to convey necessary information. While it is front-loaded, it lacks substance and is under-specified rather than concise.

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?

Given the tool has 4 parameters, no annotations, no output schema, and no schema descriptions, the description is severely incomplete. It does not explain what the tool does, how parameters interact, or what the return value is.

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%, so the description must compensate. It only mentions that session_id or path is required, but does not explain mode, process, or the meaning of the parameters. This is insufficient for 4 parameters.

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 says 'Inspect/process transform pipeline' but does not define what a transform pipeline is or what inspecting/processing entails. It is vague and fails to distinguish from sibling tools like 'analysis.status' or 'disasm.linear'.

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 only states 'Requires session_id or path' but gives no guidance on when to use this tool versus alternatives, such as other analysis or binary inspection tools. The sibling list is extensive and no context is provided.

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