kiem_tra_ket_noi

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful scope context (it verifies both pyRevit and live Revit sessions hosting the agent) plus the prerequisite ordering, but does not describe failure/error behavior when Revit is absent.

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?

Two short sentences with zero padding, and the key action plus the 'call first' directive are both front-loaded and immediately scannable.

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?

With no parameters, full annotation coverage, and an output schema that documents the return structure, the description supplies everything needed to call it correctly. Only the failure-mode expectations are left implicit.

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 tool takes zero parameters, so the baseline is 4 — there is nothing for the description to disambiguate, and the schema (empty object) matches the tool's purpose.

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 ('Kiểm tra' / check) and resource (pyRevit and Revit sessions running the agent host), so the agent knows this is a connectivity/environment probe. It is clearly distinguishable from all sibling tools, which are data-query and parameter-setting operations, though it never names a sibling.

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?

'Gọi đầu tiên' (call first) gives explicit, actionable sequencing guidance — this is a prerequisite probe before invoking the statistics/volume tools. It provides clear when-to-use context but no when-not or alternative routing, since no sibling overlaps.

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