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

With no annotations provided, the description carries the full burden, and it does well: it explicitly states 'Read-only', identifies the authentication mechanism (X-API-Key), names the HTTP method/endpoint, and enumerates the return fields. It does not mention rate limits or pagination, but for a zero-parameter status endpoint this is not a significant omission.

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 compact and information-dense, with no filler. It front-loads the core purpose, then covers authentication, response content, read-only behavior, and the endpoint in just a few sentences. Every clause adds value.

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, read-only status tool with no output schema, the description is complete: it states the operation, the auth requirement, the endpoint, the read-only nature, and the full set of returned metrics. An agent has enough to invoke it correctly and interpret the response.

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 input schema has zero parameters and 100% description coverage, so there are no parameter semantics to explain. The description still adds relevant context by explaining that identity is derived from the API key rather than from request parameters, which is useful beyond the empty schema.

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 states a specific resource ('contributor standing') with a clear verb ('Returns'), names the exact fields returned, and distinguishes this as the caller's own status rather than a general or aggregated view. It also names the endpoint and HTTP method, making the operation unambiguous.

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 phrase 'Your OWN' implies this is for checking your own contributor stats, and 'Read-only' signals a safe query, but there is no explicit statement about when to choose this over sibling tools like contribute_submissions or contribute_receipts. Usage context is implied rather than fully articulated.

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