godot_profiler

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

No annotations are provided, so the description carries the full burden. It discloses 'auto-allow' and 'game must run' but does not explain the behavior of each action (e.g., what snapshot returns, whether series starts a measurement). This is insufficient for a profiling tool.

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 extremely concise (one sentence) and front-loaded with the core purpose. Every part adds value, but the terse format sacrifices clarity on details that could be expanded.

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 complexity of a profiling tool with multiple actions and parameters, the description is incomplete. It does not specify return values (no output schema), error conditions, or detailed parameter formats. The context of 'game must run' is useful but not sufficient.

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 schema has no descriptions (0% coverage). The description adds meaning by listing possible action values (snapshot, series, spikes) and hinting at params like duration_ms, metrics, threshold_ms. However, it does not specify types or structure (e.g., whether metrics is a list or string).

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 'Performance profiling' and lists specific actions (snapshot, series, spikes), distinguishing it from sibling tools that focus on editing or reading scenes/nodes. However, it does not explicitly differentiate from other profiling tools if any exist.

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 mentions 'auto-allow, game must run' as prerequisites, implying when to use the tool (during gameplay). However, it lacks explicit guidance on when not to use it or alternatives among sibling tools.

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