Sole trader details

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds a partial view of the payload (three named fields), which is mild behavioral value but says nothing about auth requirements, whether the caller must be the account holder, or what happens for non-sole-trader accounts.

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 short fragment with no filler; the key qualifier 'sole trader' is front-loaded. It loses a point for being an incomplete sentence that never states the action being performed.

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 the description carries the burden of describing the return value; it names only three fields, leaving unclear whether name, address or identifier data are also included. For a no-parameter read tool this is close to adequate but noticeably thin.

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 zero parameters, so per the rubric the baseline is 4. The description correctly implies the tool is implicitly scoped to the authenticated account holder rather than taking an identifier.

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?

It identifies the specific resource (sole trader account holders) and enumerates the data returned (trading name, business category and subcategory), which distinguishes it from the sibling get_business_details, get_individual_details and get_joint_account_details. However, it is a noun fragment with no verb, so the retrieval action is only implied rather than stated.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the closely related siblings (get_account_holder, get_business_details, get_individual_details) that an agent must choose between. The only cue is the phrase 'sole trader account holders', which the agent must interpret on its own.

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