github_connection_status

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

With no annotations provided, the description carries full transparency burden. It discloses the read-only nature implicitly by stating it 'checks' and 'returns', but does not explicitly mention that it has no side effects or what happens if authentication fails. The return content is clearly described.

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, front-loaded sentence with no wasted words. It directly states what the tool does and what it returns, making it efficient and easy to parse.

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 parameterless status-check tool with an output schema, the description is sufficiently complete. It explains the primary purpose and return content, though it does not address error cases or authentication failure behavior. The output schema likely covers return structure, so this is adequate.

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, so schema coverage is trivially 100%. The description adds meaning beyond the schema by clarifying the purpose and output (account and rate-limit state), which is useful for an agent despite no parameters needing explanation.

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 a specific verb ('Check'), names the resource ('GitHub authentication'), and states the return value ('connected account plus rate-limit state'). It clearly distinguishes from siblings like 'health' and 'server_info' by focusing on authentication status.

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 implies when to use the tool (when needing auth/rate-limit status) but does not explicitly mention alternatives or exclusion conditions. There is no guidance on when NOT to use it or how it differs from similar tools like 'health'.

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