get_render_count

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'track' render counts, implying a read-only action, but gives no details about return format, whether it requires a running application, or any side effects. This is a significant transparency gap for a tool with zero annotation coverage.

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, front-loaded sentence with no wasted words. It quickly communicates the tool's purpose. The minor typo ('re-re-renders') does not detract from its overall conciseness and clarity.

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?

Given the absence of an output schema and annotations, the description should explain what the tool returns or how to interpret the render counts, but it does not. The simplicity of the tool (two optional parameters) is offset by the missing return-value information, leaving the agent uncertain about the expected output.

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?

Both parameters (threshold and componentName) have clear descriptions in the input schema, achieving 100% schema description coverage. The tool description itself adds no parameter-specific details, but the baseline of 3 is appropriate since the schema already documents the parameters adequately.

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 function: tracking component render counts to identify unnecessary re-renders. It uses a specific verb ('track') and resource ('component render counts'), distinguishing it from sibling tools like get_slow_components by focusing specifically on render count analysis.

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 implies usage when the goal is to identify unnecessary re-renders, but it does not explicitly state when to prefer this tool over alternatives such as get_slow_components or get_component_state, nor does it mention exclusions or prerequisites. The guidance is implicit rather than explicit.

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