RuntimeGetProfilerTraceData

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read operation ('Read') and states it returns parsed JSON, but it does not elaborate on side effects, permission requirements, or potential limitations. While not misleading, it lacks depth for a complete behavioral picture.

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 that front-loads the core purpose and key capabilities. Every word serves a purpose; no redundant or irrelevant information. It is optimally concise for quick comprehension.

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 lack of output schema and annotations, the description adequately covers the basic function but leaves gaps. For instance, it does not explain how parameters interact (e.g., 'id' only for statements view) or detail the JSON output structure. It is sufficient for a straightforward read tool but could be more comprehensive.

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 the baseline is 3. The tool description adds context by linking the views to profiler trace data categories, but it does not significantly expand on the parameter meanings beyond what the schema already provides.

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 profiler trace data by trace id/uri, specifies the available views (hitlist, statements, db accesses), and mentions it returns parsed JSON. This distinctly sets it apart from sibling tools which perform other operations like activate, create, delete, etc.

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 guidance on when to use this tool versus alternatives like RuntimeAnalyzeProfilerTrace or RuntimeCreateProfilerTraceParameters. There are no explicit conditions, prerequisites, or caveats mentioned, leaving the agent without direction for tool selection.

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