get_system_status

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

There are no annotations, so the description must carry the full burden of disclosing behavior. It fails to mention whether this is a safe read operation, what data is returned, or any side effects, offering only a static label.

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?

Three words is under-specification rather than conciseness. The description lacks any useful structure, front-loading, or informative content that would help the agent understand the tool's purpose.

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 many status-related siblings, this description is completely insufficient. It does not describe what 'system status' includes, the return format, or any operational context, making the tool's behavior opaque.

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 zero parameters and the schema fully covers them (vacuously), so the description does not need to explain parameters. The minimal description does not add parameter info, but none is required.

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 'ASTRA System Status' is a short label that restates the tool's name without a clear verb or resource scope. It does not differentiate from sibling tools like get_platform_status or get_metrics, leaving the agent unsure what specific status it retrieves.

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?

No usage guidance is provided. The description gives no indication of when to choose this tool over alternatives such as get_platform_status, wm_status, or get_metrics, making it hard for the agent to make an informed selection.

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