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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read only. Changes nothing.' is partly repetition. What the description adds is genuinely useful: the data is the canonical 'locked' brand view, not a draft, plus the concrete contents of the payload including verbatim example notes.

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?

Front-loaded with the trigger, then the return contents, then a safety line. The closing 'Read only. Changes nothing.' is two short sentences saying nearly the same thing and partly duplicates the annotations, a minor inefficiency in an otherwise tight definition.

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, so the description carries the burden of describing the return value, and it does so concretely by enumerating the fields and giving example note strings. Nothing further is needed for an agent to call a zero-argument read tool correctly.

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 tool takes no parameters, so the baseline is 4. The description correctly says nothing about inputs and spends its words on what is returned instead.

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?

States a specific resource (the brand record Suara holds) and its scope precisely: name, voice, audience, colours, offerings and stored notes. The phrase 'how their posts will sound' separates it from the sibling post-listing tools like get_my_posts or my_social_accounts.

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 a clear triggering condition ('when the signed-in owner asks what Suara knows about their business'). It does not name an alternative tool or an exclusion, but the use case is narrow enough that the trigger alone routes the agent correctly.

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