Get GitHub API rate status

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

The description discloses the caching behavior and that it separates GitHub primary rate-limit evidence from local request-governor state, adding useful context beyond the annotations. However, the phrasing 'locally paced governed' is awkward and could be clearer.

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 reasonably concise and well-structured with two sentences, but the phrase 'locally paced governed' is verbose and confusing, slightly detracting from overall clarity.

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?

The description provides enough context for a simple diagnostic tool, including its purpose, caching, and output separation. It does not mention error cases, but given the tool's simplicity and no parameters, this is acceptable.

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 no parameters, so there is nothing to explain. The description does not need to add parameter details, and the schema fully covers this aspect.

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 that the tool is a read-only diagnostic for fetching GitHub API rate limit status, and it distinguishes itself from sibling tools by focusing specifically on rate limits and local request-governor state.

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 explains its caching behavior and that it does not create additional GitHub requests, but it does not explicitly state when to use this tool versus alternatives. The usage is implied but not directly contrasted with other tools.

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