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

No annotations are provided, so the description carries the behavioral burden. The 'get' verb and reference-style framing make this clearly a read-only retrieval, and the description discloses what data will come back (colors, typography, personality, dos/donts). It does not explicitly state 'this makes no changes' or cover auth/rate-limit edge cases, but for a branded-content getter these gaps are minor.

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 description is front-loaded with the core purpose and content list, then adds usage timing and a sibling-tool pointer. It is three sentences and mostly dense, though the phrase 'the brand page might as well not exist' is more rhetorical than actionable and adds slight noise.

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?

There is no output schema, but the description compensates by enumerating the major return categories. It also provides the call context, the priority ordering, and the complementary tool for writing style. For a single-parameter read tool, an agent has enough to invoke it correctly and know what to expect.

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%: companyId is already described as the FreedomOS company id and membership requirement. The tool description only reinforces 'the company's' brand guidelines and adds no new parameter-level meaning, so the baseline 3 is appropriate.

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: get the company's brand guidelines, then enumerates the actual contents (name, tagline, colors, typography, personality/tone, naming rules, dos/donts). It also implicitly distinguishes itself from get_voice_profile by scoping this tool to how the brand looks and what it stands for. This is far more specific than a generic 'get' tool.

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?

The description gives explicit when-to-use guidance: call it before ANY operator-facing artifact, with concrete examples such as Plays, Focus copy, cards, images, banners, video, and marketing. It also proactively names the alternative get_voice_profile for writing voice/cadence/reading level, so an agent can route correctly without guessing.

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