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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds two things they don't: the Bearer accessKey auth requirement and an explicit statement that sharing/publishing is out of scope. It still omits anything about output format or limits, so it isn't fully rich.

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 short sentences, front-loaded with the returned data before auth and scope caveats; nothing is padded. The telegraphic 'Bearer accessKey.' fragment is slightly terse but costs almost no length.

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 no output schema and no parameters, the description carries the return-value burden and does so by naming the four data categories returned. Combined with the auth and scope notes, an agent has enough to call it, though the overlap with contribution_access_status remains unresolved.

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 takes zero parameters, so per the baseline there is nothing for the description to disambiguate and no schema gap to compensate for.

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 verb 'Read' plus a concrete enumeration (installation credits, authorized source hosts, scope expiration, rewards) tells the agent exactly what data comes back. However, it never differentiates itself from the near-identically named sibling 'contribution_access_status', leaving the agent to guess which one to pick.

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?

Usage is only implied by the read framing, and the one explicit boundary ('Does not enable sharing or publish') is a negative capability statement rather than a when-to-use rule. No alternative sibling is named for the overlapping 'access status' case.

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