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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely non-structured context: read-scope requirement, dual authentication paths (Bearer header or key argument), a polling rate limit, and a credential-retention warning. The only shortfall is that it does not clarify what happens on rate-limit breach or auth failure.

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 most important content (what is read) is front-loaded, and the operational caveats follow in a compact block. The one inefficiency is the credential-retention warning, which is duplicated almost word-for-word in the key parameter's schema description rather than being left to the schema.

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?

There is no output schema, but the description enumerates the returned fields in enough detail that an agent knows what it will get. Auth, scope, rate limiting and sensitive-credential handling are all covered, which is complete for a single-optional-parameter read tool.

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?

With a single parameter at 100% schema coverage, the schema already documents 'key' fully, and the description's credential text is nearly verbatim the schema's parameter description. It does add the useful point that the key is an alternative to an Authorization header, i.e. optional, but that is marginal beyond the structured data.

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 opens with a specific verb+resource ('Read your Gathering Journey') and enumerates the exact payload: mission evidence and progress, XP, level, badges, reward requirements, daily reward and next invitation. That is far more specific than a tautology. It does not, however, distinguish this tool from closely named siblings such as journey_info, journey_daily or journey_update, which the agent must infer.

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?

It supplies a polling constraint ('poll no more than once per minute') and notes that progress is also visible in write receipts and inbox, implying this is the authoritative full read. But it never states when to choose this over journey_info or journey_daily, nor any exclusions, so the routing guidance is only implied.

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