simplisafe_get_pins

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

Discloses that PINs are returned in cleartext and that the call puts them into the conversation. The 'readOnlyHint' annotation is consistent, and the description adds value by warning about sensitivity and the fallback behavior without confirmation.

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 sentences, each earning its place. First sentence states purpose and scope. Second sentence explains the confirm gating and sensitivity. No filler.

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 read tool with two parameters and no output schema, the description sufficiently covers return values (cleartext PINs), input behavior, and safety warning. No missing context needed for an agent to invoke it correctly.

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 coverage is 100%, but the description adds meaningful context: it explains the effect of 'confirm' (warning vs. actual retrieval) and the optionality of 'sid' based on number of systems. This goes slightly beyond the schema descriptions.

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 reads user PINs (master, duress, named users), which is a specific verb and resource. It distinguishes from sibling tools like 'simplisafe_get_settings' or 'simplisafe_list_sensors' by being the only PIN-reading tool.

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 explains the confirm-gated nature: without 'confirm: true' it returns a warning and does nothing. Warns that PINs are live alarm codes in cleartext, advising caution. No alternative tool is named, but no sibling duplicates this function.

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