InspectManagedAssembly

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that IL bytes are optional and bounded, which is useful behavioral detail, but it does not disclose permissions, failure modes, or output limits beyond that.

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?

A single front-loaded sentence with no filler. It is efficient and every word contributes, though for a 5-parameter tool with no schema descriptions it is arguably undersized rather than fully appropriate.

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 5 undocumented parameters, no output schema, and no usage guidance, the description is too thin to tell an agent how to invoke the tool correctly. It covers the tool's broad purpose but omits parameter meaning, required inputs (none are required), and when this inspection should be preferred over siblings.

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 all 5 parameters, so the description must compensate. It hints at type/method tokens and optional bounded IL bytes, which loosely maps to max_types, max_methods, and include_il, but it says nothing about path, module, or the meaning of the numeric bounds.

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 (Inspect) and resource (CLR metadata, type/method tokens, bounded IL bytes). It clearly identifies the domain of managed assembly inspection, though it does not explicitly differentiate itself from siblings like CaptureManagedRuntimeState, DumpModule, or DisasmRange.

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?

Provides no guidance on when to use this tool versus alternatives such as CaptureManagedRuntimeState or DumpModule. The agent can infer it targets managed assemblies, but no explicit context, prerequisites, or exclusions are given.

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