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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description adds value by disclosing the returned field set and that the issuer is scoped to 'the API key' (i.e., implicit credential-bound identity), plus the underlying endpoint GET /v1/issuer/details. It omits auth requirements and rate/credit-consumption behavior.

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?

Very short and front-loaded with the resource identity, then uses compact fragments for the field list and endpoint. Every clause carries information, though the trailing endpoint fragment is slightly redundant with the tool name.

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, the description appropriately carries the return-value burden by listing the fields and glossing 'certificate_left' as remaining credential credits. For a zero-param read tool this is nearly complete; it stops short of noting that a valid API key is mandatory (error behavior otherwise).

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?

Zero parameters, so the baseline is 4 and there is nothing for the description to clarify. It correctly implies no input is needed, consistent with the empty schema.

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?

Names a specific verb+resource ('Get the issuer (account)') and goes further by enumerating what the resource contains (id, name, e-mail, credits, language, URL). It is clearly distinguishable from siblings like accredible_get_credential or accredible_get_design, and even names the backing key the object belongs to.

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?

'Good first call' gives real sequencing guidance — an agent knows this is a sensible bootstrap step before per-resource calls. No alternatives are named, but no sibling retrieves the issuer account, so there is no competing tool to route away from.

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