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

Goes meaningfully beyond the annotations by disclosing cost mechanics ('1 account credits per successful call', 'Repeated calls may charge again') and a trust warning about returned data. The repeated-charge note is consistent with idempotentHint=false and is exactly the kind of billing/retry context annotations cannot express. It stops short of rate limits or payload shape.

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 purpose before cost and safety notes. Every sentence carries distinct information with no padding; the only minor slack is that the cost sentence could be tightened.

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, the description should at least gesture at what the aggregate statistics contain, and it does not. Purpose, params, cost and trust posture are covered, but the return shape for a stats endpoint remains undisclosed, leaving a real gap for an agent consuming 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?

Schema description coverage is 100%, so all three parameters including returnFields are already documented in the schema, making 3 the baseline. The description restates the office/text scoping but adds no format hints (e.g. accepted office codes, whether text is a literal or query expression) beyond what the schema already provides.

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 ('Retrieve aggregate trademark statistics') and names the two scoping axes (office and query text). The word 'aggregate' implicitly separates it from siblings global_brand_detail, global_brand_list and global_brand_range, though it never names them explicitly.

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?

Usage is only implied: the tool needs an office and a query text, which tells the agent the invocation shape. Nothing states when to pick this over global_brand_range or global_brand_detail, so the agent is left to infer from the resource noun alone.

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