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

No annotations exist, so the description carries the burden. It clearly signals a read operation ('Get') and sets expectations for returned content categories such as style, DOs, AVOIDs, exemplars, and reading level. It does not describe the exact return structure or behavior when no voice profile exists, but for a simple read-only fetch that is a minor gap.

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 contents, then provides usage context and sibling differentiation. Sentences like 'the copy might as well not have a brand' are rhetorical, but nearly every sentence contributes either purpose, when-to-use, or comparison with get_brand_guidelines.

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 read tool with no output schema, the description covers what is returned at a category level and when to use it. It stops short of describing the exact return shape or what happens if no voice profile has been created yet, which would make it fully 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 only parameter, companyId, is fully described in the schema with its FreedomOS id, membership requirement, and company-scoped nature, giving 100% schema description coverage. The description adds only the possessive 'company's,' which is consistent but not a meaningful semantic addition beyond the schema.

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?

Opens with a specific verb-resource pairing ('Get the company's VOICE PROFILE') and enumerates the contents: style, DOs, AVOIDs, exemplars, and target reading level. It also explicitly distinguishes itself from get_brand_guidelines by contrasting writing voice with visual brand, which helps an agent separate the many sibling get_* tools.

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?

Gives an explicit trigger: 'Use before ANY operator-facing copy: Plays, Focus, Command Center cards, posts, captions, emails, articles.' It also tells the agent not to rely on brand tone adjectives and directs it to get_brand_guidelines for visual identity, providing a clear alternative/companion routing.

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