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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond them by naming the connection prerequisite and listing the specific returned configuration areas, though it does not elaborate on response structure or edge cases.

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 and front-loaded: it states what is read, marks the operation read-only, clarifies boundaries, and gives the connection prerequisite. Each sentence contributes information without redundant restatement.

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 configuration tool with no output schema, the description provides enough context to invoke it correctly: it identifies what is returned, confirms read-only behavior, states the connection requirement, and excludes unrelated operations. Nothing essential is missing.

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 no parameters, so there are no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on behavior and returned content rather than inputs.

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 gives a specific verb ("Reads") and resource (the connected project's configuration) and enumerates the exact configuration fields returned: site URL, Pixel ID, token status, and saved checkout answers. It also rules out adjacent concerns like plan approval, callback verification, activation, and Meta receipt, making the tool's scope clear among many siblings.

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 states an explicit prerequisite ("Requires a connected site") and clearly excludes what the returned configuration and token status are not. It does not, however, name a concrete alternative sibling tool for related setup checks, so the routing guidance is strong but incomplete.

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