Anthony Hunt · SHAART Agency

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

The annotations already declare this as a safe, idempotent read operation. The description adds the domain context that these are contact options for a free diagnostic call, and does not contradict any annotations.

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?

One compact sentence conveys the full resource list and the optional-parameter behavior. There is no wasted text and the key information is front-loaded.

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 single-optional-parameter read-only tool, the description fully covers what the agent needs: what data will be returned and how to control it. No output schema is needed because the return content is explicitly enumerated.

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 schema already documents the channel parameter with 100% coverage, providing a baseline of 3. The description adds meaningful guidance by explaining that omitting the parameter returns all channels, enriching 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?

The description clearly states what the tool returns—email, phone, WhatsApp, and a booking link—using a specific resource. It is immediately distinguishable from siblings like get_pricing and list_posts by its focus on contact channels.

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 'Omit channel to get all' provides concrete usage guidance for the optional parameter. It does not explicitly name alternatives or exclusions, but the domain is clear enough that an agent knows when to call this tool.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context: the data is public, prices are in USD, both one-time and monthly options exist, and the response includes inclusions, exclusions, and a purchase page. This goes beyond the annotations without contradicting them.

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 concise sentences with no filler. The main return content is front-loaded, and the parameter behavior is stated clearly and efficiently.

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?

This is a simple tool with one optional parameter and no output schema. The description sufficiently explains what the response contains and how to get all plans versus a specific one. Nothing critical is missing for an agent to call it 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 coverage is 100% and the schema already describes plan_id as 'Return only this plan or add-on.' The description adds meaningful behavior by stating 'Omit plan_id to get everything,' clarifying the default behavior when the optional parameter is not provided.

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 clearly identifies the resource: public plans and add-ons with prices in USD, billing frequency, inclusions/exclusions, and purchase page. It does not explicitly differentiate from sibling tools like list_services, but the resource is specific enough that an agent can understand what this tool returns.

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 no guidance on when to use this tool versus siblings such as list_services or get_contact_options. It only explains the optional plan_id parameter behavior with 'Omit plan_id to get everything,' which is parameter usage rather than tool-selection guidance.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful behavioral context: it lists only published posts and explains pagination via next_cursor, which the agent needs to know. It does not contradict annotations and provides extra operational details.

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?

The description is two sentences with zero wasted words. It front-loads the core purpose and immediately gives the ordering and pagination details. It is appropriately sized for the tool's simplicity.

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 simple read-only list tool with no output schema, the description covers content scope, ordering, and pagination. It does not describe the response fields, but that is often inferred for a list operation. Combined with strong annotations, the information is sufficient for an agent to use it 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 coverage is 100% for all three parameters (lang, limit, cursor), so the baseline is 3. The description mentions pagination via next_cursor, which reinforces the cursor parameter's purpose, but it adds no new meaning beyond what the schema already specifies. It is adequate but not enhanced.

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 clearly states it lists published blog posts about GoHighLevel, AI automation, and marketing, with newest first. This specific verb and resource set it apart from siblings like get_contact_options or get_pricing, which serve different purposes. It leaves no ambiguity about what the tool does.

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 clear context (published posts, topics, ordering) but does not explicitly mention alternatives or when not to use it. Since the sibling tools are clearly unrelated, the lack of explicit exclusion is acceptable, but it stops short of a 5 by not naming any alternatives.

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

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered structurally. The description adds useful behavioral context by specifying the output shape (description and URL) and the default behavior when no tag is provided. However, it does not disclose additional runtime traits such as ordering, result limits, or error conditions, so the added behavioral depth is moderate.

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?

The description is compact: one sentence conveys both the resource and the output fields, and immediately follows with the key usage note about the optional tag. Every word earns its place, and the most important information is front-loaded.

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 only one optional parameter, a fully described enum, and annotations covering safety and idempotency, the description provides the essential missing pieces: the return contents and default filtering behavior. No output schema is present, but the description compensates by naming the fields an agent can expect. Nothing critical is missing for correct invocation.

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 coverage is 100% and the tag parameter already has a clear description and a full enum. The description goes beyond the schema by explicitly stating the default behavior when the tag is omitted ('Omit tag to get all'). This gives the agent actionable parameter guidance that is not present in the schema alone.

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 clearly identifies the tool as returning the services this business provides, with each service's description and page URL. This distinguishes it from siblings like get_pricing and list_posts, which cover different resources. The resource and verb are both specific and unambiguous.

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 establishes clear context: use this tool when you need the business's services and their associated pages. It gives a default behavior ('Omit tag to get all') that clarifies the optional parameter, though it does not explicitly discuss when to prefer this over sibling tools. The intended use case is still evident without needing exclusions.

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