Hide the setup checklist

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

The description explains the primary effect (hides the card) and the parameter's influence on that effect. It does not discuss potential side effects or permissions, but given the simple, non-destructive nature (as reflected in annotations), this level of transparency is adequate.

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 concise and front-loaded, stating the core action first. It uses two sentences to cover both the primary use and parameter behavior, with no unnecessary 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 simplicity of the tool (one boolean parameter, no complex side effects), the description provides all necessary context: purpose, usage scenario, and parameter behavior. No additional information is required for correct invocation.

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 only parameter, 'show', is explicitly explained in the description: 'Pass show=true to bring it back.' This fully clarifies its meaning and usage, providing complete semantic coverage for the parameter.

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 action (hides) and the specific target (the 'Get set up' card on the household dashboard). It also provides a concrete example scenario, distinguishing it from other tool purposes in the same family.

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 gives explicit guidance on when to use it (e.g., when the owner says they don't need the setup card) and explains the reverse behavior (pass show=true to bring it back). This is sufficient for an agent to decide when to invoke it.

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