esphome_clean_mqtt

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing side effects, authorization needs, what 'stale' means, or whether the operation is reversible. For a deletion tool, this is insufficient.

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 very short (one sentence) and front-loaded with the action. However, it lacks structure (e.g., breaking into purpose, usage, behavior) and could be more efficient by including key details without added length.

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 has an output schema, return values are covered. However, with no annotations and a single parameter, the description is incomplete. It does not specify prerequisites, when to run, or how 'stale' is determined, leaving gaps for an AI agent.

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 0%, so the description must compensate. It mentions the tool is 'for an ESPHome device' but does not explicitly map the 'name' parameter to a device name or provide format details. The description adds minimal meaning beyond the schema.

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 ('Remove'), the resource ('stale MQTT discovery entries'), and the target ('for an ESPHome device'). It also specifies the mode ('MQTT mode only'), distinguishing it from other ESPHome tools like compile, upload, or validate.

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 the tool is for MQTT mode only but does not explicitly state when not to use it or name alternatives. No guidance on prerequisites or context beyond the mode qualification.

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