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

Annotations already indicate the tool is not read-only, not destructive, and closed-world, but the description adds no behavioral context. It does not explain whether the analysis is synchronous or asynchronous, what side effects or state changes occur, whether the tunnel must be active, or how results are obtained after invocation.

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, front-loaded sentence with no wasted words. It communicates the core action and scope efficiently, even though it is terse.

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 non-read-only analysis tool with three required parameters and no output schema, the description is too sparse. It omits important context such as tunnel prerequisites, asynchronous processing behavior, and what an agent should do after invoking it, leaving significant gaps for correct orchestration.

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%, so all three parameters (port, tunnelId, tunnelName) are already documented in the schema. The description adds no syntax, format, or semantic detail beyond what the schema provides, making the baseline score of 3 appropriate.

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, 'Analyzes,' and a specific resource, a locally running app, with the additional qualifier 'for accessibility via TestMu AI tunnel.' It is clear enough for an agent to understand the tool's basic purpose, but it does not differentiate from related sibling tools such as buildLocalAppForAnalysis, checkAppProcessingStatus, or getAccessibilityReport.

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 'locally running app ... via TestMu AI tunnel' implies a usage scenario, but there is no explicit guidance on when to use this tool versus alternatives or prerequisites. It does not state, for example, whether a tunnel must already exist, whether a build step is required, or how this differs from retrieving an accessibility report.

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