get_login_status

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

No annotations are provided, so the description carries the full burden. 'Check' and 'view' imply a safe read operation, and the two-mode behavior (status vs. login instructions) is disclosed, but the description says nothing about auth requirements, what the response contains, or how the two modes are selected given there are no input parameters.

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?

A single front-loaded sentence with no filler. The compound 'or' structure slightly blurs the tool's two roles, but overall it is efficient and readable.

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?

For a zero-parameter, read-only status tool with no output schema, the description is largely sufficient: it covers both capabilities and implies a safe check. A brief note on the return shape or the relationship to login_cpanel would make it complete.

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. The description adds the meaningful note that the single call can yield either connection status or login instructions, which is the only semantic content needed for a parameterless tool.

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 and resource ('Check if cPanel is currently connected') and adds a second capability ('get login instructions'). An agent can tell it's a status/introspection tool, though it doesn't explicitly differentiate itself from siblings like verify_cpanel_connection or login_cpanel, which overlap conceptually.

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 phrase 'Check if cPanel is currently connected' implies usage as a pre-flight check, and the 'or get login instructions' branch hints at a fallback when not connected. However, no explicit when-to-use vs. when-not guidance or named alternatives are given, so the agent must infer the relationship to verify_cpanel_connection and login_cpanel.

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