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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value by disclosing the return content (rules, media counts/lengths, max_length, a settings JSON schema, lookups) and that it is 'Free,' which is genuinely beyond the annotations. However, it is muddled and omits any note on error behavior or shape consistency.

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?

The sentence is dense yet hard to parse, and it wastes space on the duplicated, uninformative "Free. Free." The return-content enumeration is front-loaded poorly into a run-on parenthetical rather than structured clearly.

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 does attempt to describe what comes back (rules, max_length, settings JSON schema, lookups), which is the right job. But the delivery is cryptic and the 'lookups (for social_channel_lookup)' clause and doubled 'Free' leave an agent guessing at the exact return structure.

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 100% and the single channel_id parameter is fully documented in the schema (pattern, length, source). The description adds nothing about the parameter, so baseline 3 applies.

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 gestures at the resource ("What a channel's network accepts: its rules... max_length, the settings a post may or must carry"), but the phrasing is oblique and never states a clean verb like "returns" or "reads." Combined with the title it is decipherable, but the description alone is vaguer than a clear verb+resource statement, and it does not cleanly distinguish itself from social_channel_lookup or social_channels.

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?

There is no explicit when-to-use or when-not guidance. The only sibling reference, "its lookups (for social_channel_lookup)," is a note about the return payload, not a routing instruction, so an agent gets no help deciding between this tool and social_channel_lookup/social_channels.

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