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

Annotations already cover read-only, idempotent, closed-world, and non-destructive, so the bar is lower. The description still adds genuine behavior: a strict "never invent a brand fact" constraint on downstream use and the explicit null return when no profile exists, both of which are not derivable from annotations.

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?

Purpose is front-loaded and the trailing directives are short and actionable. The long enumerated clause is information-dense but partially overlaps the output schema, keeping it just short of ideal tightness.

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 an output schema present, the description need not explain the return shape, yet it usefully previews the brand categories. Combined with annotations and a zero-parameter schema, an agent has enough to call it correctly, with the only real gap being sibling disambiguation.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter-semantics gap for the schema to fill. Schema coverage is 100% and nothing in the description needs to compensate.

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 ("Get") and a richly qualified resource (the connected account's saved business identity, voice, visual style, and content strategy), then enumerates the concrete contents. An agent knows exactly what this returns without opening the schema.

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 guidance and no routing to alternatives; siblings like soclo_brand_read, soclo_brand_status, and soclo_brand_scan are never mentioned, which is a real ambiguity given how similar the names are. The only directives ("use exactly as saved", null when unsaved) describe handling of the result, not when to select this tool.

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