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

Annotations already establish readOnly and closed-world behavior, and the description goes well beyond that by enumerating returned fields (title, keywords, published, changed, paused, engagement stats) and explaining what paused and changed mean. It also discloses the help_url construction, which is useful operational context not present in the schema.

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 content is front-loaded with the core resource definition, but the field list is packed into a dense run-on sentence and could be organized more clearly. It is informative but not maximally concise.

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?

No output schema exists, so the description carries the burden of explaining return values; it does this well by naming the fields and clarifying status indicators and help_url format. It stops short of describing pagination, ordering, or limits, which leaves a small gap for a list tool.

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?

There is one parameter and schema coverage is 100%; the schema already says product_id is the site's uuid and comes from list_products. The description adds no parameter-specific meaning beyond that, so the baseline of 3 applies.

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 defines the resource clearly as a site's help articles and explains what they are and how they surface, which lets an agent distinguish this from get_article or save_article. The listing verb itself is only implied by the name, not stated in the description, so it falls short of a perfect 5.

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 only usage-relevant guidance is the plan prerequisite 'Pro and higher'; there is no explicit statement of when to call this instead of get_article or other article tools, and no exclusions. The agent must infer the listing use case from the name and resource description.

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