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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so 'Read only.' is pure repetition. What the description does add beyond annotations is the precedence rule that the owner's own rules and preferences outrank best practice — meaningful guidance for how to act on the output — but it says nothing about freshness, whether values can be missing, or how the account-scoped view differs in content from the whole-business view.

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?

It is front-loaded reasonably, but the whole definition is a single sprawling sentence built from an eleven-item list of contents, several items of which (economics sub-metrics, per-account goal/target/budget) could be compressed. The closing 'Read only.' is redundant with annotations and wastes the final position.

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?

An output schema exists, so return shapes need not be explained, and the description plus the parameter description together cover scope and read-only safety adequately. Missing only explicit routing relative to sibling context tools, which for a foundational read tool is a real but modest gap.

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 coverage is 100% and the single parameter's description already spells out the account-scoped vs whole-business distinction. The description adds no syntax, defaults, or behavioral detail beyond that, so the baseline 3 applies.

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 enumeration (offer, area, customers, voice, economics, per-account goals/budgets, owner rules, prior attempts, open questions) makes it unambiguous that this returns the stored business profile. The framing is metaphorical ('the business card every Taseli decision starts from') rather than a clean verb+resource, and it never names a sibling it is distinct from — notably it does not distinguish itself from get_brand_kit, which plausibly overlaps on 'voice'.

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: it is 'where every Taseli decision starts from', suggesting to read it before proposing changes. There is no explicit when-to-use, no when-not-to-use, no routing to get_brand_kit, get_memory, get_plan or get_account_review, and no mention of calling it with vs without the account parameter as a usage decision.

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