tally_connection_status

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

With no annotations provided, the description carries full responsibility. It discloses that the tool is 'strictly read-only', cannot modify TallyPrime, and explicitly states what it does and does not return. It also lists the exact response elements (endpoint, RTT, wire format, encoding, error code) and that pagination is not applicable.

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 well-structured with labeled sections (WHEN TO USE, RETURNS, DOES NOT RETURN, PAGINATION) and every sentence adds value. The opening line immediately states the purpose, making it highly scannable for an agent.

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 parameters, no output schema, basic health-check functionality), the description covers all necessary context: purpose, usage guidance, return contents, exclusions, read-only safety, and pagination. Nothing important 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?

There are zero parameters and the schema covers all of them trivially, so the baseline for 0 params is 4. The description adds meaning by explaining what the tool checks and returns, which is more relevant than any parameter documentation.

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 states 'Check whether TallyPrime is running and reachable over its HTTP interface' with a clear verb and target. It clearly distinguishes this health-check tool from the many data-retrieval siblings like tally_list_companies or tally_get_ledger.

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?

Explicit 'WHEN TO USE' section says to use it as a first step when other Tally tools fail or to confirm setup before analysis. It also notes 'Cheap and safe to call at any time.' The 'DOES NOT RETURN' section tells when not to use it and points to a sibling (tally_list_companies) for company information.

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