session_reseller_config

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

With no annotations, the description carries the behavioral disclosure burden. It communicates the auth context and implies a read-only config lookup via 'Current', but does not explicitly state that it has no side effects, what happens when an admin uses it, or any other behavioral constraints. The output schema covers return structure.

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 compact sentence with a parenthetical qualifier. Every word earns its place: it states the resource, the access condition, and implies retrieval without any 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?

For a zero-parameter getter with an output schema, the description is largely complete: it names the resource and the required role. It could add a little more nuance about admin behavior or confirm that it returns the current context's reseller configuration, but these are minor gaps.

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?

There are zero parameters and schema coverage is 100%, so there is no parameter information for the description to add. The description appropriately focuses on purpose and access context rather than repeating an 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?

The description identifies the resource ('reseller config') and the access context ('when logged in as reseller/admin'), and the word 'Current' implies retrieval. It distinguishes itself from the sibling session_user_config by specifying the reseller/admin scope, though it lacks an explicit verb like 'get' or 'return'.

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 parenthetical 'when logged in as reseller/admin' gives clear context for when this tool is appropriate. It does not explicitly state when not to use it or point to session_user_config as an alternative, but the access-role condition is sufficiently clear.

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