TCS system status

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description does not need to restate that. It adds the scope of what is checked (profile, connection, runtime, TCS commands, path limits), which is useful, but it gives no further behavioral insight such as return format, potential latency, or whether a connection is required.

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 sentence of 13 words, front-loaded with the verb 'Check'. Every word earns its place, listing exactly what the tool examines. It is appropriately sized for a status-check tool and avoids redundancy or filler.

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 tool with no parameters, strong annotations, and no output schema, the description is fairly complete. It clearly states what is checked. However, it does not explicitly mention what the tool returns (e.g., a status report, errors, or success indicator), which could be ambiguous. Still, the tool name and 'Check' imply it retrieves status, so it is nearly 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 has 0 parameters, so the baseline is 4. The input schema is empty, and the description correctly does not attempt to explain parameters. The listed items (profile, connection, etc.) are aspects of status, not parameters, so the description adds no parameter semantics but none are needed.

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 uses the verb 'Check' and specifies the resource as TCS system status, listing concrete aspects: profile, connection, runtime, TCS commands, and configured path limits. This distinguishes it clearly from sibling tools focused on jobs, files, or commands, and the title 'TCS system status' reinforces the purpose.

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios. The sibling list offers context, but the description itself lacks any 'use this when' or 'for other details use X' statements, leaving usage entirely implicit.

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