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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Free; changes nothing' largely restates structured data. The one genuine addition is the 'Needs read:brand' scope requirement, which tells the agent an authorization prerequisite exists; nothing is said about the shape or size of the returned list.

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 clauses with the action front-loaded and no filler. Slightly redundant repetition of the no-side-effects point (already covered by readOnlyHint) keeps it from being maximally efficient.

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?

For a one-parameter listing tool with no output schema, the description covers the essentials but never says what a 'Strategy target' looks like or how many come back, which matters for an enumeration endpoint an agent must feed into a later save call.

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?

Only one parameter, and the enum of business/creator/personal is already fully specified in the schema. The description clarifies that the account type determines which target set is returned, which adds slight semantic value, and matches the baseline for a fully-enumerated single parameter.

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 states a specific verb and resource: list the app's Strategy target choices, scoped to an account type. This is clear enough to distinguish it from nearby tools like soclo_creative_preferences_save (a mutation) and soclo_creative_preferences_read, though it does not explicitly name that read 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: an agent can infer this is a discovery/lookup step before saving preferences, but there is no explicit 'use this when...' or 'use X instead.' No prerequisites or ordering relative to soclo_creative_preferences_save are stated.

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