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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful but limited context by listing what the profile contains, though it doesn't clarify whether channels and staffers are embedded in the response or require follow-up calls to sibling tools.

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 efficient sentence with the resource named first and the contained fields listed after. No filler, though the nominal phrasing is slightly less direct than a verb-led definition.

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 needn't be explained, and the description usefully summarizes them anyway. However, the missing slug semantics leave a real gap for a required-input detail tool, keeping this at minimum-viable completeness.

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% and the single 'slug' parameter is undocumented in both schema and description. The description gives no hint about slug format or where an agent obtains one, so it fails to compensate for the coverage gap.

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 names the specific resource (a Fanatics Live shop's public profile) and enumerates its contents (description, social links, follower count, channels, staffers), so an agent knows this is a detail lookup, not a search. It is not a verb phrase, but the noun-plus-fields framing is unambiguous enough to distinguish it from the plural fanaticslive_shops list tool.

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 guidance and no alternatives are named. Nothing tells the agent how this differs from fanaticslive_shops, fanaticslive_channel, or fanaticslive_shop_shows, or when to prefer one over the other.

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