analyze_home

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

No annotations exist, so the description must convey behavioral traits. It fails to indicate whether actions are read-only or mutating, side effects, or authorization needs. The list of actions implies some are queries, but safety_audit or orphans could be destructive.

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 but poorly structured; it uses a colon and comma-separated list without clear grouping. While front-loaded with 'Home-wide analysis', the bulk is dense and hard to scan.

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 complexity (9 actions, 4 parameters, no output schema, no annotations), the description lacks critical details such as return values, prerequisites, and the full scope of each action. It leaves significant gaps for agent decision-making.

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 description clarifies which parameters apply to which actions (e.g., 'days' for stale_items, 'roomName' for find_equipment), adding value beyond the schema's brief descriptions. This reduces ambiguity for parameter usage.

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 'Home-wide analysis' and enumerates specific actions (health, safety_audit, etc.), making the tool's purpose clear. However, it lacks a main verb and could be more explicit about the general function.

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?

No guidance is provided on when to use this tool vs. alternatives like 'manage_item' or 'query_things'. Without usage context, the agent may choose the wrong tool.

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