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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds genuine context beyond them: no key/authentication is required, and crucially that the call neither collects data nor grants transmission or publication permission. That last point is the kind of side-effect clarification annotations cannot express.

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 core action is front-loaded, but the remainder is a single dense clause chain ('qualifying read rewards, scoped public-source submission, and local review before a selected-report preview') that is hard to parse on first read. It is compact but not well structured, and some of the nominalized phrasing earns little.

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, the description carries the burden of telling the agent what it gets back. It gestures at the content areas but never describes the actual return shape or format, so an agent knows the topic but not the payload. Adequate for a zero-param read call, but with a clear gap.

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 this dimension scores 4. There is nothing for the description to add, and it introduces no parameter-related confusion.

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?

Names a specific verb (Read) and resource (the public-knowledge exchange offer) and enumerates the content it covers: rewards, source submission, review, report preview. It does not explicitly differentiate itself from siblings like get_contribution_status or contribution_access_status, but 'offer' vs 'status' is a discernible distinction.

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?

'Optional' signals this is not mandatory, and 'No key required' gives a prerequisite, but there is no explicit when-to-use rule and no named alternative (e.g., prepare_contribution or get_contribution_status) for the adjacency. Usage is implied rather than guided.

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