power

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

Discloses one behavioral trait: summary automatically saves snapshots per call. However, with no annotations provided, the description could better indicate side effects, auth needs, or whether operations are read-only. Lacks comprehensive transparency.

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?

Well-organized with a lead sentence, bullet list of subfunctions, and an args section. Every sentence earns its place, though slightly verbose; could be tightened slightly without losing 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 tool's complexity (5 parameters, multiple modes) and the presence of an output schema (unshown), the description covers all subfunctions and parameters sufficiently, leaving no gaps in understanding.

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 descriptions coverage is 0%, yet the description explains each parameter's role (action, block_name, output_path, format, session_id) and defaults, adding crucial meaning beyond 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?

Description clearly states the tool is for unified power query/export, listing all subfunctions (summary, block_power, rails, thermal, clock_power, export_report) with brief explanations, making purpose highly specific and distinguishable from siblings.

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?

Provides context for each action and its required parameters (e.g., block_name for block_power), but does not explicitly mention when to use this tool over alternatives like power_design or estimate, nor does it state when not to use.

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