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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. Beyond that, the description adds real value by disclosing the returned field set and explicitly bounding scope ('No secrets or contact details'), which is meaningful because no output schema exists; only the serialization format and error behavior remain unstated.

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, the returned fields listed first and the scope exclusion second. Every clause carries information; the only minor inefficiency is that the field list arrives without a leading verb to anchor it.

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?

For a zero-parameter, read-only tool with no output schema, the description supplies the one thing the structured data cannot: what fields come back and what is deliberately excluded. What remains missing — response shape and whether values are cached — is minor at this complexity.

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 does not waste space restating argument semantics that do not exist.

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?

The description enumerates exactly what the tool returns — name, industry, location, goal, plan tier, subscription status, credit balance — which makes the resource unambiguous. It reads as a noun phrase rather than a verb+resource, so the action ('get') is only implied by the name, and it does not explicitly contrast with siblings, though the resource is clearly distinct from ad accounts, campaigns, and reports.

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: an agent can infer this is the tool for business-level context (account tier, subscription status) before drilling into ad-level siblings. There is no explicit when-to-use statement, no mention of alternatives, and no prerequisites or caveats such as whether it should be called once per session.

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