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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the trailing 'Read-only.' is redundant. However, the description adds genuinely new behavioral context that no structured field carries: the returned brief can be incomplete, signaled by a 'complete false' flag, and in that case the agent should ask the questions supplied. That is exactly the kind of state-dependent guidance annotations cannot express.

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 and contents are front-loaded, and every clause describes a real section of the brief, so the long enumeration earns its length. Minor waste remains in the redundant trailing 'Read-only.' and in the slightly run-on comma list, which could be broken into two or three shorter sentences for easier scanning.

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 no parameters, the description carries the burden of explaining what comes back, and it does: it enumerates the brief's fields and explains the completion flag and the required follow-up action. For a zero-argument read tool this is about as complete as an agent needs before calling it and acting on 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, so there is nothing to disambiguate and the baseline of 4 applies. The mention of 'complete false' concerns the returned payload, not an input, so it neither helps nor hurts parameter semantics.

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 concretely what the resource is and enumerates its contents: name, what it sells, hours, locations, prices and links, FAQs, tone, languages, never-promise rules, escalation contacts. An agent immediately knows this is the business's operating profile rather than any of the account/profile/media siblings. No ambiguity about the verb (read) or the resource.

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 an explicit trigger: 'Read it before replying to a customer and follow it,' which tells the agent when to call and how to use the result. It also covers the incomplete case ('complete false means it still needs filling: ask the questions it gives'). It stops short of naming an alternative tool or a when-not condition, so it is clear context rather than full routing guidance.

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