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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the payload contents (pillars, formats, duration, hooks, instructions), which usefully stands in for the absent output schema, but it discloses nothing about defaults, auth, or behavior when preferences are unset.

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 front-loaded sentence that enumerates return fields with zero filler. Every clause earns its place.

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 simple annotated read tool with no output schema, enumerating the returned fields is genuinely helpful and largely compensates for the missing output schema. However, the undocumented brandId and the total absence of usage context leave the definition only minimally complete.

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 single parameter brandId has 0% schema description coverage, and the description does not compensate — it only obliquely implies 'the brand's' via the possessive. It never explains what brandId is, its format, or what happens when it is omitted (the schema marks no required params).

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?

Specific verb ('Get') plus resource ('the brand's script preferences') and an explicit enumeration of what the resource contains. It reads unambiguously against its counterpart update_script_preferences, though it never names or contrasts with that sibling directly.

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?

No guidance on when to call this versus alternatives. With generate_scripts, generate_hook_options, and update_script_preferences in the sibling set, the description should say something like 'fetch before generating scripts' or 'read counterpart of update_script_preferences', but it offers nothing.

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