tally_status

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

No annotations exist, so the description carries the full burden. It discloses what the call surfaces (connection state, loaded companies, backup settings), which implies a read-only diagnostic, but never states that explicitly nor describes what a failed connection returns or whether the call is side-effect free.

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 a clear verb ('Check') and no filler. Every clause identifies a distinct output of the call.

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?

With no output schema and no annotations, the description must convey return shape, and it only names the three outputs at a high level. It leaves unclear how 'backup settings' relates to the sibling list_backups/backup_data tools and what the response looks like when the connection is down.

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 of 4 applies; there is no parameter semantics 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?

States three concrete operations: connectivity check to TallyPrime, listing loaded companies, and surfacing backup settings. This clearly distinguishes it from the create_/alter_/list_* siblings, though the combination of three distinct outputs in one tool blurs the single-resource framing.

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?

Usage is implied rather than stated — an agent can infer this is a diagnostic/preflight tool to run before other operations, but the description never says when to call it or that it should precede the mutating siblings. No alternatives or exclusions are named.

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