nodejs_profile

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

With no annotations, the description must fully convey behavioral traits. It mentions 'built-in Node.js profiler' but fails to disclose performance impacts, resource usage, or whether the tool is read-only. The mutation nature of profiling (creating files) is implied but not explicitly stated.

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?

A single concise sentence with no fluff. However, it could be more informative without being verbose. The structure is front-loaded but lacks additional details.

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 profiling tool with no output schema and no annotations, the description omits important context such as output file details, interpretation of results, or any side effects. It is insufficient for an agent to fully understand the tool's behavior.

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% with all parameters described in schema. The description does not add extra meaning beyond the schema parameter descriptions. Baseline 3 is appropriate.

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 uses the verb 'Profile' and resource 'Node.js application performance', clearly indicating the tool's function. It distinguishes from sibling tools like nodejs_benchmark, though it could be more specific about profiling types (e.g., CPU, heap) which are only apparent from the schema.

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?

No guidance is provided on when to use this tool versus alternatives such as nodejs_benchmark or other profiling tools. The description neither suggests prerequisites nor scenarios for profiling.

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