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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safe-read profile is covered structurally. The description adds that the return is the 'full text' of a single item and enumerates id namespaces (activity:, page:, faq:), but says nothing about truncation, size limits, or error behavior for a missing id.

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?

One sentence, front-loaded with the verb and resource, with the id-format hint in parentheses. Nothing is redundant and no filler is present.

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?

An output schema exists, so return values need not be explained, and the description correctly characterizes the result as full text of a single record. The main residual gap is disambiguation from the sibling activity_details tool, which the description does not address.

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?

Schema description coverage is 0% for the single 'id' property, so the description must carry the load; the 'activity:…, page:…, faq:…' prefix enumeration does add real meaning about accepted id forms. It stops short of stating whether the prefix is mandatory or whether a bare id is accepted, leaving ambiguity.

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?

States a specific verb ('Fetch') and resource ('the full text of one search result') plus the addressing key ('by its id'), which is concrete enough to distinguish it from a listing/search tool. It does not explicitly differentiate itself from the similar-sounding siblings activity_details or find_activity, keeping it below a 5.

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 'one search result' implies this is the follow-up step after search, which is useful implied guidance. However, it never says when to prefer it over activity_details or find_activity, and no prerequisites or exclusions are stated.

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