shelter_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context by framing the call as a snapshot and listing the exact categories returned, which helps the agent set expectations about the response. No contradiction with annotations.

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 one clear, front-loaded sentence. The em-dash list efficiently conveys scope without filler, and every phrase adds useful information.

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 read-only status tool with one optional parameter, no output schema, and strong annotations, this description is sufficiently complete. It conveys what the snapshot contains, though it does not describe output format or the caching/refresh behavior in prose; the schema covers refresh adequately.

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 description coverage is 100% for the single optional refresh boolean, so the schema already fully documents the parameter. The description's 'snapshot' wording indirectly relates to caching, but it adds no parameter-specific detail beyond what the schema provides.

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 uses a specific verb ('Get') and resource ('financial status'), then enumerates concrete components: safe-to-spend, balances, upcoming bills, health score. The word 'snapshot' clearly distinguishes this current-state tool from outcome-focused siblings like shelter_forecast and shelter_runway.

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?

Usage is only implied: the agent can infer this is for pulling a current financial status snapshot. However, the description gives no explicit when-to-use guidance or alternatives, despite many adjacent sibling tools such as shelter_forecast, shelter_alerts, and shelter_affordability.

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