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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is lighter. It adds real value by disclosing the default_site return and the embedded routing rule, but it never explains what the 'context pack' itself contains or how large it is.

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 primary purpose and followed by the usage recommendation and the secondary return. No filler, though the parenthetical rule text is slightly dense.

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 and zero parameter documentation, the description carries the full burden and only partially meets it: it explains one return element but leaves all three inputs and the bulk of the return payload undefined. For a tool meant to be called before content generation, that is a meaningful 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?

Three parameters (query, domain, site_id) with 0% schema description coverage, and the description mentions none of them. An agent has no idea whether query is a search string, a prompt, or a content topic, nor how domain and site_id interact with the returned default_site.

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 verb and resource ('Get AI context pack for content generation') and adds a concrete secondary return ('default_site' with id, domain, and routing rule). It is distinguishable from siblings like get_brain or get_brand_voice, though 'AI context pack' remains somewhat abstract about what is actually returned.

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 when-to-use cue ('Recommended before creating tweets/posts'), which is genuinely actionable. However, it names no alternatives and no exclusions, so an agent cannot tell why it should call this rather than get_brain, get_brand_voice, or get_account_context.

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