godot_capture_profiler_trace

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

The description only states the purpose and does not disclose what happens after recording (e.g., output format, side effects). Annotations indicate readOnlyHint=true, so safety is covered, but the description adds no additional behavioral context beyond the purpose.

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, focused sentence without unnecessary words. It clearly states the action and purpose, making it easy to parse.

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 simple tool with one parameter, the description adequately conveys what it does. It lacks details about the output or return type, but given no output schema and the tool's straightforward nature, it is sufficiently complete.

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?

The parameter frames_to_sample has a full description in the schema, explaining its meaning. The tool description does not mention the parameter, but the schema covers it, so the description does not need to add more. Baseline 3 applies.

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 verb 'record' and the resource 'engine frame timeline trace slices' with a specific purpose ('performance bottleneck analysis'). It differentiates this tool from siblings like godot_get_performance_metrics, which is a different action.

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 implies usage for profiling and checking performance, but does not explicitly compare to alternatives like godot_get_performance_metrics or describe when not to use. The intent is inferable but not explicitly stated.

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