simplisafe_list_systems

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. Because there is no output schema, the description usefully carries the return-value burden by naming the fields surfaced per system (alarm state, alarming status, connectivity, power) and the sid hand-off to downstream tools.

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 tight sentences with no filler. The capability statement comes first and the routing hint ('Start here...') is front-loaded at the end of the opening sentence pair, so both key facts are immediately visible.

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 parameterless read-only list tool with no output schema, the description covers purpose, returned fields, and the sid hand-off well. It omits any note on account scoping, pagination, or behavior when no systems exist, which are minor gaps.

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 tool takes zero parameters, so the schema has nothing to document and the baseline for this dimension is 4. The description correctly adds no parameter guidance, which is appropriate here.

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 verb and resource ('List the SimpliSafe systems on this account') and enumerates what is returned: alarm state, alarming status, connectivity, power. The 'Start here' clause distinguishes it from siblings like simplisafe_get_system and simplisafe_list_sensors, so an agent can tell them apart without opening schemas.

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?

Explicitly positions this as the entry point: 'Start here to get the `sid` other tools take', which tells the agent when this tool is the right first call. It does not name an alternative to avoid or state exclusion conditions, so it stops short of full when/when-not guidance.

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