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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description usefully adds the endpoint and the framing that this is pre-authorisation enrolment, but it does not say what happens to an existing credential on 'refresh', whether it requires auth, or how failures surface.

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 front-loaded sentence with the action first, then audience, then route; nothing is padded or restated. It could be tightened only marginally, e.g. the endpoint parenthetical could be dropped if the server details cover it.

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?

There is no output schema so return values need not be explained, and annotations cover the mutation profile. The remaining gap is the request body: the description and schema both punt to an external OpenAPI resource, so an agent has no in-band hint about required fields for an enrolment call.

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?

Only one parameter (body) and schema description coverage is reported at 100%, so the baseline is 3. However, the schema text is merely a deferral ('See the AffixIO OpenAPI schema resource for the contract'), so the description adds no field-level meaning beyond what the schema pointer provides.

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?

Specific verb pair ('Create or refresh') plus a precise resource ('AffixIO agent-trust credential') and scope ('for an AI agent ... for a user or merchant'), with the HTTP route supplied. It is clearly distinct from siblings like affix_agent_trust_verify or affix_agent_trust_authorise, though it never names those siblings to make the contrast explicit.

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?

'before it acts for a user or merchant' gives an implicit timing condition that tells the agent when this is needed in a flow. There is no explicit when-not guidance, no mention of prerequisite steps (e.g. prerequisite identification of the agent) and no pointer to the alternative tools (verify/authorise/audit) if a credential already exists.

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