hsportal_info

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 only states 'read-only', which indicates no mutation but does not explain side effects, response format, or any prerequisites. For a no-parameter tool, this is a minimal but insufficient disclosure of behavior.

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 a single concise phrase, appropriately short for a tool with no parameters. The key attribute 'read-only' is front-loaded, and there is no extraneous text. It lacks sentence structure but remains effective in brevity.

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 has no parameters and no output schema, the description alone must convey what the agent can expect. It merely says 'hotspot portal info' without detailing the content of that info (e.g., connection counts, settings, health status). This is insufficient for an intelligent agent to decide whether to call it or interpret the response.

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, so the description is not required to clarify parameter semantics. The baseline of 4 applies because the schema fully covers the (empty) parameter set and there is no missing parameter information to compensate for.

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 names a specific resource ('hotspot portal') and states it is 'info' (read-only), clearly differentiating it from hsportal_setup. However, it does not specify what kind of info (e.g., status, configuration, statistics), leaving some ambiguity about the exact data returned.

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 guidance is given on when to use this tool versus alternatives like hsportal_level or hsportal_setup. The read-only tag implies a query, but no explicit context or exclusions are provided, leaving the agent to infer usage from the name alone.

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