RuntimeAnalyzeProfilerTrace

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

Without annotations, the description carries full burden. It only says 'Read', implying non-destructive, but omits behavioral traits such as prerequisites, side effects, or whether the tool requires specific permissions or system access.

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, very concise. It covers the main purpose but could benefit from a slightly structured breakdown (e.g., separate input/output details).

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 no output schema, the description only mentions 'totals + top entries' which is vague. For a tool returning a summary, more details about the output structure would improve completeness. The parameter count is moderate but the description is sparse.

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 75%, falling below the high threshold. The description adds no extra meaning to the parameters beyond their schema descriptions, such as clarifying the role of 'view' or 'top' 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 clearly states the tool reads a profiler trace view and returns a compact analysis summary with totals and top entries. This distinguishes it from sibling tools like RuntimeGetProfilerTraceData, which likely returns raw 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?

No explicit guidance is provided on when to use this tool versus alternatives (e.g., RuntimeGetProfilerTraceData). The description does not mention context or exclusions, leaving the agent to infer usage.

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