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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description nonetheless adds genuinely new context — the required read:brand scope, the zero-cost aspect, and the fact that the response carries an expectedRevision (a concurrency token the agent will need). It doesn't describe the empty/unconfigured state, which keeps it below a 5.

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 compact sentence front-loads the resource list, then appends cost, side-effect, permission and revision-token facts. Every clause carries distinct information with no repetition.

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 and no parameters, the description adequately conveys what comes back (direction, templates, goals, expectedRevision), that it is free and side-effect-free, and the required scope. Only the behavior when nothing has been saved yet is left unaddressed.

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; there is nothing for the description to disambiguate. The description spends its words on return contents instead, which is appropriate for a no-arg reader.

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 enumerates the resources returned: saved creative direction, content template choices and Strategy goals, plus the current expectedRevision. This clearly distinguishes it from soclo_creative_preferences_save and soclo_creative_preferences_targets, though neither sibling is named explicitly.

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?

"Free; changes nothing" and "Needs read:brand" give the agent cost and permission context, and the mention of expectedRevision implies it is a precursor to a save. However, no explicit when-to-use, when-not, or sibling routing (e.g., 'call before soclo_creative_preferences_save') is provided, so the workflow relationship is only implied.

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