hl_perp_deploy_auction_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to state that this is a read-only query, what data it returns, or any side effects. The description simply names the resource without any behavioral context.

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 cryptically short, but the single sentence adds no value beyond the name. It is under-specified rather than genuinely concise, and it fails to earn its place by providing useful information.

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's simplicity (no params, output schema exists), the description is still too sparse. It does not explain what the status entails, how it relates to deploy auctions, or what the output represents. The agent receives minimal orientation.

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 has zero parameters and schema coverage is 100%, so there is no parameter information missing. Baseline for 0 params is 4, and the description does not need to add parameter semantics since there are none.

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 'Perp deploy auction status (perpDeployAuctionStatus)' is essentially a tautology, restating the tool name with an alias. It lacks a verb or explicit action, so it does not clearly state what the tool does or return. It only hints at the perp vs. spot distinction via the word 'Perp'.

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 provides no guidance whatsoever on when to use this tool versus alternatives such as hl_spot_deploy_auction_status or other status tools. There is no mention of use cases, prerequisites, or exclusions.

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