compare_applications

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

With no annotations, the description carries the full burden and does well: it discloses the selection heuristic (task-named app if installed, else first installed substitute), that ranking is 'usual first choice', that installation status is included, and that the tool is advisory only. It omits any mention of read-only/auth characteristics, but the content disclosure is unusually rich.

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?

Front-loaded with the core purpose and usage pattern, but the ~27-item parenthetical domain list is dense and occupies most of the text. It is informative rather than filler, yet it blurs the line between conciseness and completeness.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers invocation modes, advisory semantics, and output shape. For a 2-param read tool this is close to complete; only the absence of sibling routing leaves a minor gap.

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 coverage is 0% and both parameters are bare strings with empty defaults, so the description must compensate, and it does: it explains that area takes an area id and task takes a description used to match areas. It does not map concrete area id values, but the enumerated domains supply that context.

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?

States a specific verb+resource ('head-to-head comparison of the applications that can do the same kind of task') and enumerates the task domains it covers, so an agent knows exactly what it returns. It does not, however, distinguish itself from the sibling recommend_application, which appears to serve a related advisory 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?

Explicitly gives three invocation modes (no args = list areas, area=<id> = one area, task=<description> = match areas) and clarifies the advisory nature ('Any installed candidate may be used; tell the user which trade-offs apply'). It stops short of stating when to prefer this over recommend_application or list_software.

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