controlShow

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false). The description adds one genuinely non-redundant fact: it requires a trusted owner and an interactive Windows x64 desktop. It does not disclose what state is changed, reversibility, or failure behavior, so it adds modest value over the 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?

A single short sentence, but the first clause merely echoes the tool name and the platform token, wasting part of its already minimal budget. The one useful clause (environment requirement) is present and not buried.

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 mutation tool with no output schema, the description should at least say what the call returns or how success/failure surfaces, and what 'showing' a control means for the target window. It covers only the environment precondition, leaving the operation's effect and result undocumented.

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?

All three parameters (title, control, text) carry 100% schema description coverage, so the schema already defines them. The description adds no parameter meaning, syntax, or matching semantics beyond what the schema provides; baseline 3 applies when the schema does the heavy lifting.

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 is essentially a restatement of the tool name ('Windows AutoIt controlShow') plus a platform tag. It never states in plain terms what the operation does (e.g., makes a previously hidden control visible), so an agent must infer the verb's meaning from the AutoIt function name alone.

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 when-to-use guidance, no conditions, and no comparison to the many sibling control tools (controlHide, controlClick, controlSetText, controlGetText). The environment note hints at preconditions but gives no routing logic between this and controlHide or the other control* siblings.

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