get_brand_context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says the tool returns the full brand DNA but does not mention whether data is cached, how recent it is, any access constraints, or that the operation is strictly read-only. The lack of such details is a gap for a tool that agents might rely on for strategic decisions.

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 a single sentence, well-structured, and front-loaded with the tool's purpose and a list of contents. Every word contributes meaning, with no redundancy or fluff.

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 zero-parameter getter with no output schema, the description provides a clear list of what is returned and a usage context. It is sufficiently complete for typical use, though it could mention limitations (e.g., data freshness or scope) to fully cover edge cases. Overall, it meets the needs of an agent selecting this tool.

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?

With zero parameters, the baseline is 4. The description adds value by enumerating the content categories returned, which is helpful context even though there are no input parameters to explain. The schema is empty and fully covered (100%), so no additional parameter documentation is needed.

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 clearly identifies the tool as retrieving the user's complete brand DNA, listing specific elements (name, category, audience, etc.). This is a specific resource-level verb ('get') with clear scope, distinguishing it from sibling tools that target competitors, ads, or playbooks.

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?

It provides a usage context ('Use for any strategic brand question') but lacks explicit when-not-to-use guidance or mention of alternatives. While the broad scope is implied, it doesn't compare against other knowledge tools like get_context_ledger or get_brand_briefing, leaving room for ambiguity.

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