ms_ping

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

Describes the return format on success ('ok, status, data') and error ('canonical error envelope'). Annotations provide readOnlyHint and openWorldHint, and description adds behavioral details without contradiction.

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?

Two sentences: first states purpose and operation, second explains response and usage. Front-loaded, no wasted words.

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?

Given zero parameters and an output schema, the description sufficiently covers the tool's behavior. It explains the purpose, the response envelope, and usage context. Sibling tool differentiation is implicit via the specific endpoint mentioned.

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?

No parameters in schema, so baseline is 4. Description adds context about the underlying GET request (assortment?limit=1), providing useful implementation detail beyond 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?

Explicitly states 'Live connectivity + auth check' and mentions the specific API call 'GET assortment?limit=1'. Title from annotations further confirms 'MoySklad live auth check'. Distinguishes from sibling tools like ms_check_auth by specifying the endpoint.

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?

Directly advises 'Use this on the cabinet to confirm the token before anything else', giving clear when-to-use context. Does not explicitly exclude alternatives, but the instruction implies it is the first step.

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