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 covered. The description goes beyond that by enumerating the exact payload surface (config fields, allowed crawlers, requests so far, limit, percent used, reset date) and the negative space, which is genuinely useful behavioral context for a quota-state tool. It stops short of stating auth requirements or rate limits on the call itself, so it is not a 5.

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?

Front-loaded: the one-line purpose and the setup-vs-analysis framing come first, followed by the payload inventory and the negative-space routing. The closing Args block is somewhat redundant with the schema's required list, which is the only waste in an otherwise tight definition.

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, so the description must carry the return-value burden — and it does, enumerating every field group returned. Combined with the explicit exclusions and sibling routing, an agent has everything needed to select and 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?

Schema description coverage is 50%: user_intent is documented in the schema, but brand_id has no schema description, and the description's 'brand_id: The brand to check (required)' is only marginally more informative than the field name plus the required list. The description does partially compensate for the coverage gap, which is the minimum bar, but adds no format or constraint detail.

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 the brand's AI Pages connection state and monthly usage') and immediately frames the scope ('This is setup and quota, not analysis'). It explicitly names the sibling tools that cover adjacent purposes (get_perception, get_actions), so an agent can distinguish it from the other 60+ tools without opening a schema.

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 an explicit when-not ('It does NOT return positioning, strengths, weaknesses, opportunities, or themes') and routes the agent to the correct alternative for each excluded need ('for how AI describes the brand use get_perception; for recommendations use get_actions'). That is a complete decision rule, not an implied one.

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