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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds two genuinely non-structured facts — that data comes from the hosting instance specifically (federation behavior) and that the call costs 1 credit — but says nothing about not-found/error handling, caching (relevant given the cache_max_age param), or latency.

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?

Three short sentences: identification, payload/manifest, cost. Front-loaded with the tool's identity and free of filler. The field list is dense but earns its place by substituting for an absent output 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?

With no output schema, listing the returned fields is a real contribution. However, the undocumented second parameter and the absence of any failure-mode or caching note leave gaps for a tool that is open-world and depends on a third-party instance's availability.

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 only 50%: 'handle' is well documented in the schema, but cache_max_age has no description anywhere and the description does not mention it or explain its semantics. The description also adds no meaning to 'handle' (e.g. whether a bare name without instance works) beyond what the schema already says.

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 (reads) and resource (a PeerTube channel's public profile) and enumerates the fields returned (followers, following, video count, avatar, banner, creation date), so an agent immediately knows this is metadata, not content. It is distinguishable from peertube_channelVideos by implication, but the description never explicitly names that sibling.

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?

Usage is only implied: it's plainly the tool for channel metadata, and 'read from the instance that hosts it' hints at federation scope, but there is no statement of when to prefer it over peertube_channelVideos, peertube_search or peertube_video, and no prerequisites or exclusions.

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