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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Get GitHub system status,' which implies a read-only operation as the sole behavioral trait. It does not mention whether this hits an external API, whether authentication is needed, rate limits, or any side effects.

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 appropriately short for a no-argument tool, using just a few words to convey the action and target. The '[COST: ]' prefix is an empty placeholder that adds no value, but the rest is free of redundancy.

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 zero-parameter tool with an output schema, the description is minimally sufficient for invocation. However, the complete absence of usage guidance, behavioral caveats, or any hint about what the status payload contains leaves some context gaps that a richer description could fill.

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 coverage is 100% (vacuously). The baseline for a zero-parameter tool is 4, and the description does not need to add parameter details since none exist.

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 clearly states a verb ('Get') and a resource ('GitHub system status'), so an agent can understand the tool's core function. It distinguishes from sibling tools like get_cloudflare_status by naming GitHub, though it does not elaborate on what 'system status' includes or what the response represents.

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?

There is no guidance on when to use this tool versus alternatives, such as get_cloudflare_status or other status/weather/fetch tools. The intended use is only implied by the tool's name and description, not explicitly stated.

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