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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: it returns current state (not a historical snapshot), strategicGoal is null when absent, and a Topic ID input is refused. It stops short of describing pagination or full response shape, but that is largely handled by the output schema.

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?

Purpose is front-loaded in the first clause, followed by tightly packed, information-bearing sentences. The parenthetical enumeration of profile contents is slightly dense but every sentence reinforces scoping or provenance rather than restating the name.

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 annotations covering safety and an output schema covering return structure, the description does not need to explain response format. It still covers provenance, when to use, and sibling differentiation, leaving nothing essential for correct invocation missing.

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 description coverage is 0% for the single siteId parameter, so the burden falls on the description. It compensates by stating that siteId comes from list_sites_and_topics with subjectKind=site and that a Topic ID is refused, effectively constraining the parameter's valid source and type beyond the raw uuid pattern.

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 ('Read one brand Site') and enumerates the returned facets (business profile, strategicGoal note, model selections). It actively distinguishes itself from siblings by noting strategy product definitions live in get_scan_config and that a Topic ID is refused (vs get_topic).

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?

'Use this read before editing and after an uncertain update' gives explicit when-to-use guidance. It also supplies when-not signals: it is not a historical scan snapshot, and a Topic ID is refused. The provenance (siteId from list_sites_and_topics with subjectKind=site) routes the agent before calling.

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