get_store_credit_account

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only restates the basic fetch operation and offers no additional context such as whether transactions are included, pagination behavior, or permission requirements. This is a significant gap for a tool that has pagination parameters.

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 a single, concise sentence that front-loads the core purpose. Every word earns its place, and there is no unnecessary filler.

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?

Despite the simplicity of the operation, the description leaves out key context such as what data the account object contains, whether transactions are returned, and how this relates to other store credit account tools. The lack of an output schema and annotations further increases the need for descriptive context, which is absent.

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 input schema provides 100% description coverage for all three parameters, including an example ID format and pagination details. The description adds no extra parameter context, but the baseline score of 3 is appropriate given the schema's thoroughness.

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 clearly states the action (Fetch) and the resource (store credit account) with the identifier method (by ID). This distinguishes it from the sibling tool get_store_credit_accounts_by_owner, which fetches by owner rather than ID.

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 context for use is clear: use this tool when you have a specific store credit account ID. However, it does not explicitly mention exclusionary cases or direct users to alternative tools like get_store_credit_accounts_by_owner for owner-based lookups.

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