apex_outlet_events

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

No annotations are provided, so the description must carry the behavioral burden. It discloses second-resolution timing and a logging-enabled filter, but omits read-only status, pagination/limit behavior, time-window defaults, and any authentication or permission requirements.

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?

Two short sentences, front-loaded with the key output characteristic and an important availability caveat. There is no wasted text.

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?

An output schema exists, so return values need less explanation, but the input side is severely under-specified: no parameter meanings, no default window/limit context, and no usage guidance. For a three-parameter tool with no annotations and 0% schema coverage, the description leaves too much for the agent to infer.

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?

All three parameters (days, limit, outlet) have zero schema description coverage, and the description does not explain any of them. It references outlets generally but never states that the outlet parameter filters results, nor does it clarify days or limit semantics.

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 resource and output: exact outlet on/off event times at second resolution. It is clear what the tool returns, though it does not explicitly distinguish itself from siblings like apex_get_outlets or apex_power_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 description implies retrieving outlet event history but gives no explicit when-to-use guidance or alternatives. The only caveat is that only outlets with logging enabled appear, which is useful but not a usage rule.

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