perf

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the tool 'shows' data, but the presence of parameters like 'action' (with values start/stop/sample) and 'kind' suggests it can initiate profiling sessions, which is not disclosed. The description does not mention if the tool is read-only, destructive, or requires specific session state.

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 concise sentence that front-loads the primary purpose. It earns its place with no redundancy.

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's complexity (28 parameters, many enums, no output schema), the description is severely incomplete. It does not explain the sub-actions (sampling, starting, stopping), return format, or dependencies on other tools/sessions. The agent lacks the context needed to invoke the tool effectively.

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 high (86%), so the schema already documents most parameters. The description adds no additional meaning beyond what the schema provides; it does not explain the relationship between parameters like action, area, and kind, which are critical for correct usage.

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 uses a specific verb ('Show') and identifies resources ('session performance, frame health, and memory diagnostics'), making the tool's purpose clear. However, it does not differentiate from siblings like 'debug', 'logs', or 'trace', which may also show performance-related data.

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 provides no indication of when to use this tool versus alternatives, no prerequisites, and no exclusion criteria. The large number of parameters (28) and sub-actions (e.g., action, subject, kind) are not mentioned, leaving the agent without guidance on how to invoke the tool correctly.

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