list_alerts

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

With no annotations provided, the description carries the full transparency burden. It discloses that results are ordered newest-first, that 'date' is in epoch seconds and follows the same convention as list_clips, and that the memo field carries AI recognition results—these are useful behavioral details beyond the schema.

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 three sentences: the first states the core purpose, the second adds valuable context about the memo field, and the third clarifies the date format. Each sentence earns its place, though the second is a bit verbose.

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 simple 2-parameter tool with an output schema present, the description covers the essential aspects: purpose, ordering, date semantics, and memo field. It does not explicitly explain the 'limit' parameter, but the schema default and output schema partially mitigate that gap.

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 schema has 0% description coverage, so the description must compensate, but it does not. It only implies the 'camera' parameter through the phrase 'for a camera,' and the 'limit' parameter is not mentioned at all, leaving the agent to guess its meaning despite the default of 20.

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 opens with 'List motion/AI alerts for a camera, newest first,' which clearly states the verb (List), the resource (motion/AI alerts), and a key behavior (newest first). It also positions the tool as the 'fast path' for identity questions, effectively distinguishing it from siblings like list_clips.

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 explicitly says this is the 'fast path for who/what triggered this camera and when,' providing clear when-to-use context. It also notes that it can answer identity questions 'without a separate face-recognition lookup,' suggesting an alternative approach, though it does not explicitly contrast with sibling list_clips.

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