Profile CEF performance and memory metrics

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description adds meaningful context beyond that: the privacy/requirements caveat that CDP tools need Pengu Loader while standard LCU REST/events/workflows do not, plus the diagnostic/non-mutating nature of the call.

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?

Four sentences, front-loaded with purpose then metrics then use cases then prerequisite. Every sentence carries information, though the parenthetical Pengu Loader note is somewhat parenthetical weight that could be trimmed.

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?

With no parameters and no output schema, the description carries the return-value burden and does so by enumerating the gathered metrics and warning flags. It also covers prerequisites and troubleshooting, leaving little an agent needs before calling it; only the exact output shape is unstated, which is acceptable here.

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 tool takes zero parameters, so the baseline is 4. The description appropriately adds no parameter guidance because none exist, and it front-loads what the (parameterless) call returns instead.

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?

States a specific verb and resource (inspect CEF performance/memory metrics for the League client frontend) and enumerates the exact metrics returned (JS heap size, DOM node count, layout/recalc counts, task/script duration, memory pressure flags). It is clearly distinguishable from siblings like lol_cdp_network_summary or lol_cdp_dom_tree.

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?

Gives concrete use cases (detect memory leaks, detached DOM nodes, renderer lag in frontend plugins) and a prerequisite plus failure fallback (CDP via Pengu Loader; check lol_status if connection fails). It does not explicitly name a preferred sibling alternative when CDP is unavailable beyond the status check, so it falls just short of a 5.

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