Hvac get results

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the state dependency on hvac_run_calc and the shape of the returned data, but says nothing about error behavior when no calculation has been run. Adequate but not 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?

The core sentence is tight and front-loaded, but the appended '[bulc-mcp rules] HVAC-001 — bulc_knowledge_search "<id>"' is a templated artifact that does not earn its place and interrupts an otherwise clean definition.

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 output schema, the description usefully compensates by enumerating the result fields returned, and it documents the prerequisite call. Only the absence of failure-mode behavior (e.g., what happens before hvac_run_calc) 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?

The tool takes zero parameters, so the baseline is 4 per the rubric. The description correctly implies a parameterless 'fetch the current results' call and adds no misleading parameter claims.

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 ('Get HVAC airflow calculation results') and enumerates the returned quantities (supply/exhaust flow, duct velocity, terminal flow ranges). It also distinguishes itself from hvac_run_calc by naming it as the prerequisite. The trailing '[bulc-mcp rules] HVAC-001' fragment adds noise rather than clarity, keeping it just short of a 5.

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 states the ordering constraint '(run hvac_run_calc first)', which is the key usage condition for this tool. It does not, however, distinguish itself from other result-style siblings such as hvac_list_summary or spr_get_results, so the routing guidance is partial.

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