shelter_alerts

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

Annotations include readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about 'active' alerts and the types of alerts, but doesn't disclose more behaviors beyond that. It doesn't contradict annotations, but adds limited value beyond them.

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 a single concise sentence that clearly states the purpose and scope. It front-loads the key verb ('Get') and resource ('active financial alerts'), and includes examples of alert types. No wasted words.

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 simplicity (one optional parameter, no output schema), the description is adequate. It explains what the tool returns (alerts) and the filtering option. It doesn't explain any return format, but since no output schema exists, some ambiguity remains, but it's minor for a simple read operation.

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%, so the single parameter 'severity' is fully documented with an enum. The description doesn't mention the parameter, but it's not necessary because the schema is explicit. The parameter is optional and has a clear enum, so no extra explanation is needed.

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's purpose: 'Get active financial alerts' and specifies the types ('unusual spending, upcoming bills, low balance warnings'). It distinguishes from siblings like shelter_status and shelter_forecast by focusing on alerts.

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 usage for checking financial alerts, but does not explicitly state when to use this tool versus alternatives. It lacks 'when not to use' guidance, but the sibling list provides context. No explicit alternatives are named.

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