Suggest Optimizations

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

With no annotations, the description carries the full behavioral burden and does so well, disclosing the analysis types, the 'always reports CPU self-time cost' invariant, and the deduplication behavior. It only stops short of stating side-effect status or return-shape details.

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 dense sentence that front-loads the core purpose and then packs high-value behavioral details without repetition or filler. Each clause earns its place.

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 no-annotation, no-output-schema tool, the description covers the key behaviors an agent needs to invoke it confidently: input, what is detected, and what is returned. It leans on the schema for parameter details and only lightly skips explicit sibling differentiation.

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 coverage is 100%, so the parameters are already fully documented. The description adds no parameter-level semantics, but none are required because profileId and limit are self-explanatory and described in the schema.

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 opens with a specific action ('Analyzes the profile') and a concrete deliverable ('returns structured optimization suggestions for the hottest functions'), making the tool's purpose unmistakable. The detection details (fan-in, recursion, V8 patterns) further separate it from siblings like get_hotspots or get_profile_summary.

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 intended use is implied: call this when you want actionable optimization guidance rather than raw hotspot data. However, it never explicitly states when to prefer this tool over get_hotspots or explain_function, and it offers no exclusions or preconditions.

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