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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the read scope (what state is surfaced), which is modest added value, but says nothing about failure behavior for an unknown activity_id or any authorization requirements.

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 front-loaded sentence with the verb and resource first and the return facets listed after the colon; no filler. The list is slightly dense but every element is informative.

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 usefully enumerates what the read returns, and annotations cover the safety profile, so an agent can call this correctly. The remaining gap is the lack of any error/not-found behavior, which is minor for a single-entity read.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents activity_id fully. The description adds no format, range, or lookup semantics beyond 'one activity'; baseline 3 applies when the schema does the work.

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 ('Read') and resource ('one activity') and enumerates the returned facets (metadata, labels, settings, quality suggestions, publish blockers), so the agent knows exactly what this returns. It does not, however, distinguish itself from overlapping siblings like get_activity_content or get_publish_blockers, whose subject matter it explicitly claims to include.

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 description gives no when-to-use framing and no alternatives or exclusions, even though get_activity_content and get_publish_blockers cover a subset of what this tool returns. An agent must infer from the name alone which of the three to call.

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