get_render_summary

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 its read-only nature by returning a summary and lists the result fields, but it does not mention error cases (e.g., invalid file path) or any edge-case behavior. This is adequate but not rich.

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 two sentences: the first lists the output components, the second gives a single actionable usage instruction. No filler or redundant detail.

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 tool is straightforward with one simple parameter, and the description enumerates all returned fields explicitly, compensating for the lack of an output schema. It also contextualizes when this should be used.

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 already describes profile_path as an absolute path to the JSON export with 100% coverage. The description adds no further meaning beyond implying the file is a Profiler export, so the schema alone sufficiently defines the parameter.

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 returns a high-level overview of a React DevTools Profiler export and enumerates the exact outputs: total commits, total render time, top 5 slowest components by self time, and total spurious render count. It distinguishes itself from sibling tools by positioning this as the first-step overview before drilling into specifics.

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 explicitly instructs 'Use this first to understand the scale of the performance problem before drilling into specifics,' which provides clear when-to-use guidance. It does not name alternative tools, but the tie to 'drilling into specifics' implies the other sibling tools are for deeper analysis.

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