tally_connection_status

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with them ('nothing here can modify TallyPrime'). Beyond that, it discloses a genuinely non-obvious behavioral trait: this tool always bypasses the response cache and explains why, so 'success' is guaranteed to mean Tally answered just now. It also enumerates the return payload and error-with-suggestion behavior on failure.

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?

Well front-loaded with the core purpose first, then labeled sections for usage, cache behavior, returns, and exclusions. It is on the long side, and a line like 'PAGINATION: not applicable' adds little, but nearly every sentence carries distinct 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?

Despite having no output schema, the description fully specifies what is returned (success flag, endpoint, server version, round-trip time, wire format, encoding, error code plus fix suggestion) and what is not returned (any accounting data, loaded company). Nothing an agent needs to call it or interpret the result is missing.

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 there is nothing to document and the baseline of 4 applies. The description correctly implies no input is needed and explicitly marks pagination as not applicable.

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 ('Check whether') and resource ('TallyPrime is running and reachable over its HTTP interface'), and explicitly distinguishes itself from siblings by noting it does not report which company is loaded and pointing to tally_list_companies for that. An agent can identify this as the health/liveness probe without opening any schema.

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?

Provides an explicit WHEN TO USE section: first step when any other Tally tool fails, setup confirmation before analysis, and for version/troubleshooting questions. It also names the alternative (tally_list_companies) for the company-listing need, so both the when and the when-not are covered.

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