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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without help from the description. The description's only contribution is scoping the returned content (app identity plus participation procedure), which is mild added value; it says nothing about caching, availability, or whether participation steps are localized.

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?

A single terse bullet-style fragment with no filler, and the most identifying content (app name) leads. It is a noun phrase rather than a sentence, so it reads slightly clipped, but nothing in it is wasteful.

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 lookup with no output schema, the description adequately conveys both the source (the stamp tour app itself) and the returned fields. The main missing piece is routing guidance against sibling tools, which a caller may still need to infer.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The field list substitutes usefully for the absent output schema by telling the agent what shape of data to expect.

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 enumerates the exact resource fields returned — app name, operator, install URL, participation steps — which is specific enough that an agent knows this is the app-level metadata endpoint, not a tour endpoint like its siblings get_tour or search_tours. It lacks an explicit verb ('returns'/'looks up') and never states it is a retrieval operation, but the field list does the disambiguating work.

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?

No when-to-use, when-not-to-use, or alternative guidance appears anywhere. Nothing tells the agent to reach for this tool when a user asks how to join the stamp tour versus calling get_tour for a specific tour's details, even though the participation-steps content makes that routing question very plausible.

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