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

readOnlyHint=true already tells the agent this is a safe read, so the description mainly adds that the returned artifact is signed and intended for publication at a specific well-known path. It does not disclose what happens for an unapproved or unverified domain (error vs. empty result), nor any auth requirements, which are the gaps an agent would actually hit.

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?

A single dense sentence with no filler, and the core action plus the publication context are front-loaded. Nothing in it is redundant with the title or 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 one-parameter read tool with no output schema and only a readOnlyHint annotation, the description covers the what and where but is thin on failure modes, auth, and what 'signed' entails for the caller. Adequate to invoke correctly in the happy path, incomplete for edge cases.

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 0% for the single `domain` parameter, so the description must compensate. It does add meaning—the domain is the approved brand domain and appears in the resulting https://<domain>/.well-known/trust.json URL—but it never states format expectations (bare host vs. full URL) which matters for a 0%-coverage string param.

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?

Uses a specific verb (Get) and a specific resource (signed CGBB Member trust.json) scoped to an approved domain, which is far more precise than the title alone. It does not explicitly distinguish itself from siblings like verify_brand or check_domain_verification, so an agent must infer that this one fetches an artifact rather than performing verification.

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 'for an approved domain' implies a precondition (domain must already be approved/verified), which is a useful usage hint. However, there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as verify_brand when the domain is not yet approved.

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