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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds a genuinely non-redundant behavioral fact — 'Does not spend credits' — which is a cost constraint an agent cannot infer from structured fields.

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?

Three short sentences, front-loaded with the resource and its contents, then consumers, then the cost note. Nothing is repeated from the schema or annotations and no sentence is filler.

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, and the description compensates by enumerating the Brain's constituent fields (website, about text, brand voice, key messages, ideal customer, competitors), effectively serving as a return-value summary. Combined with the annotation-covered safety and cost profile, an agent has everything needed to call this 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 zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description instead spends its words on what comes back, which is the more useful place for them here.

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?

Specific verb ('Read') plus specific resource ('this project's Brain'), followed by an enumeration of exactly what the Brain contains (website, about text, brand voice, key messages, ideal customer, competitors). This makes it unmistakable against the sibling update_brain, whose verb signals mutation while this one signals retrieval.

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?

The description gives concrete consumers ('Content Writer and chatbots use this context'), which tells an agent the downstream purpose of the read. It does not explicitly state exclusions or contrast against update_brain, but the read/update split is self-evident and the 'does not spend credits' line removes a common hesitation about calling it.

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