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

Annotations already declare readOnlyHint=true, but the description adds useful behavioral context: it is a single-entity synthesis, plan-gated, and based on contracts rather than marketing. It does not mention auth, rate limits, or possible failure modes, but the annotation lowers the burden.

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 information-dense and front-loads the core purpose before moving to sibling differentiation and pricing. It is somewhat heavy with formatting choices like caps and em-dashes, but every sentence contributes useful context.

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 absent and a key parameter undocumented, the description gives a partial picture: it says results are rolled up by capability with tag-level evidence, but leaves the input contract and return shape underspecified. It is adequate but has clear gaps.

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 only 50%: the slug parameter has no schema description, and the description does not explain what slug should contain or how context is used beyond the schema. The description adds no parameter-level guidance, so it fails to compensate for the low coverage.

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 states a specific verb and resource: it summarizes what one vendor's published APIs allow a business to do, rolled up by capability with tag-level evidence. It also differentiates itself from get_provider_capabilities by naming what that sibling returns, so an agent can tell them apart.

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?

It explicitly says NOT get_provider_capabilities, which is artifact counts and agent-readiness dimensions, giving a direct routing rule versus an alternative. It also clarifies plan and pricing context, which helps an agent decide when this tool is appropriate.

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