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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds 'without mutating state' (redundant with annotations) and lists what fields it reads, which is mildly useful. No auth or rate-limit context, so a 3 is appropriate.

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 sentences, front-loaded with what is inspected and followed by a concrete example. No wasted words, though the example is somewhat redundant with the schema.

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 read-only inspection tool with zero required params and full schema coverage, this is nearly complete. Without an output schema, it could note the shape of the profile/readiness data returned, but the scope is adequately conveyed.

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 the baseline is 3. The example demonstrates calling with 'context' and 'location', adding a bit of format guidance, but it doesn't explain the 'company' parameter or the location alias semantics beyond the schema.

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?

Specific verb+resource: inspects a HighLevel sub-account location profile, timezone, and readiness configuration. Distinguishes itself from agency-level siblings, though it doesn't explicitly name an alternative. Clear enough that an agent knows what it returns information about.

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 phrase 'without mutating state' implies a read-only inspection context, and the example call shows intended usage. But there's no explicit when-to-use guidance versus siblings like ghl_agency_contexts or ghl_agency_doctor, leaving the agent to infer selection.

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