Get brand profile

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one genuinely behavioral detail beyond that: the strategy section is null when none exists, which prevents misreading an empty field. It says nothing about auth requirements, error cases, or whether the profile can be entirely absent, so it is useful but thin.

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?

Every clause is informative, but the first sentence is a dense 45-word run-on with a nested parenthetical and the awkward phrase 'the content strategy as strategy (goal, positioning, ...)' that is hard to parse on one read. The short second sentence is well-placed and front-loads the action.

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?

With no output schema, the description must carry the return shape, and it does so by enumerating the profile sections and the strategy sub-fields (goal, positioning, pillar share, posts per week, lean into, avoid). Nesting depth and exact value types remain implicit, but an agent has enough to call it and interpret the result.

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 zero parameters (100% coverage, empty schema), so the baseline is 4. There is nothing parameter-level the description needs to explain, and it does not waste words inventing any.

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 enumerates the exact resource contents (voice, audience, do/don't rules, pillars, hashtags, example posts, strategy) and scopes it to 'this workspace,' which makes it unmistakable that this is the brand-profile read. It never uses a retrieval verb, so the name/title carries that part, and it doesn't explicitly contrast with any sibling.

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?

'Read it before writing any post' gives a clear, actionable trigger that an agent can apply directly before calling create_draft, ai_compose or schedule_post. It states when to use it but offers no when-not conditions and no named alternatives, which keeps it short of a 5.

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