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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description's help. The description adds the shape of the result (brands with sites and competitors), which is useful context, but says nothing about pagination, account-scoping behavior, or failure modes when the account is disconnected.

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?

Two short sentences, zero filler. The purpose and returned payload come first, and the relational note about sibling tools is placed last where it belongs.

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 must carry the return-shape burden, and it does by enumerating brands, sites, and competitors. It could say a bit more about what to do with the result or account-connection prerequisites, but this is sufficient to call the tool 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 and the baseline of 4 applies. The description correctly implies the call needs no arguments by framing the account as 'connected' and preselected.

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 ('see which brands the connected CueScout account tracks') and goes further by naming the returned content: brands, their sites, and per-brand competitors. It also signals its relationship to the sibling tool family ('The other account tools take one of these brands'), so an agent can separate it from get_profile or get_todo without inspecting schemas.

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 use context ('Use this to see...') and an implicit discovery workflow: because other account tools consume a brand, this is the entry point for obtaining one. It stops short of explicit when-not guidance or naming a specific alternative tool, so it lands just below the top band.

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