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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds that the result includes a storefront profile and public URL, but it does not disclose auth requirements, failure behavior, or whether this is tied to the current seller context. This is adequate but not rich.

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 that names the action, resource, and return contents with no filler. The parenthetical field list is efficient and every part of the sentence adds information.

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 zero-parameter, no-output-schema getter, the description is complete: it names the resource, the seller scope, the profile fields, and the public URL. Combined with the safe read annotations, an agent has enough to invoke the tool and understand the result.

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 has zero parameters and the schema has no properties, so there is nothing for the description to add about parameter meaning. The description's field list helps clarify what the returned profile will contain, which is useful given no output schema exists.

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 identifies a specific verb and resource: 'get this seller's storefront profile' and enumerates the returned fields (handle, display name, bio, branding, public URL). It is clear, but it does not explicitly distinguish itself from sibling getters like neuron_get_profile or neuron_get_business_profile, so it stops short of a 5.

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?

No guidance is given on when to use this tool instead of related read tools such as neuron_get_profile or neuron_get_business_profile. There are no exclusions or conditions, and the only contextual hint is the implicit 'this seller' framing. An agent must infer when this tool applies.

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