Verify Crown Town Compost auth + connectivity

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds valuable behavioral context: it explains the login step, dashboard fetch, and the specific output fields (authenticated, account_status, service_addresses). It also reveals the error-handling nuance of distinguishing 'no creds', 'bad creds', and 'site error', which annotations do not cover.

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, well-structured sentence that front-loads the action and compactly lists the output and error distinctions. It includes no filler and every phrase contributes meaning.

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?

The tool has no output schema, but the description explicitly enumerates the return fields and the plain-English hint types. It covers the key behavioral aspects (read-only, auth check, portal access) sufficiently for a tool of this simplicity, and no additional details are necessary.

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?

With zero parameters, the description adds no parameter-specific semantics, but the baseline for 0 params is 4. The tool requires no input, so the description's behavior description fully covers what the agent needs to know about invoking it.

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 clearly states a specific action: confirming credentials, logging in, fetching the dashboard, and reporting a structured result. It distinguishes itself from siblings like crowntown_get_account or crowntown_get_dashboard by focusing on health verification rather than data retrieval or mutation.

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 implicitly communicates when to use the tool: as a healthcheck/auth verification before performing other portal operations. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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