profiler-snapshot

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

No annotations are provided, so the description must fully disclose behavior. While it implies a read-only snapshot, it does not explicitly state safety (no side effects), permissions, or return format. This is insufficient for a safe selection by an AI agent.

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?

Two sentences, no filler, front-loaded with the action and content. Every word adds value.

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?

The description covers purpose and high-level metrics but omits details like return value structure (no output schema) or whether the tool is synchronous. For a simple snapshot tool, it is adequate but could be more 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 input schema has zero parameters, so no parameter documentation is needed. The description avoids irrelevant detail, earning a baseline score of 4 per the rubric.

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's purpose: capturing a quick performance snapshot with specific metrics (FPS, memory, etc.). It distinguishes itself from sibling profiler tools (e.g., profiler-frame-hierarchy, profiler-gc-alloc) by emphasizing a 'quick overview' of current status.

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 gives a usage context ('Useful for a quick overview of current performance status') but does not explicitly exclude scenarios or name alternative tools for deeper analysis. Implied usage is clear, but no when-not-to-use guidance.

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