nex_sms_project_list

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

readOnlyHint=true already covers the safety profile, so the description's added value is the disclosure that prices and stock are live rather than cached, and that each result carries a projectId. With no output schema, naming the returned fields is genuinely useful. It does not mention pagination, rate limits, or what an empty result means.

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 short sentences, front-loaded with the operation and its return contents, followed by the usage pointer. Nothing is redundant with the schema or annotations.

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 single-parameter read tool with annotations and no output schema, the description covers what it returns and how to chain it into nex_sms_buy. The only real hole is the origin of countryId, a prerequisite most agents would need spelled out.

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?

Schema description coverage is 0% and the single parameter countryId is undocumented anywhere, so the description has to compensate and only partly does: 'of one country' implies countryId scopes the listing. It never explains the format or how to source a valid countryId, leaving the agent to guess or call a sibling first.

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?

States a specific verb and resource ('List the projects') and immediately disambiguates the domain term with a parenthetical ('target apps/sites such as Telegram or WhatsApp'), which an agent could not infer from the name. It also names the data returned (live unit price and stock), separating it from nex_sms_country_list.

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?

Gives an explicit workflow entry point: 'Use this to pick a projectId before nex_sms_buy.' That tells the agent both when to call it and which sibling consumes its output. It stops short of stating the prerequisite step (obtaining countryId, presumably via nex_sms_country_list) or any exclusion.

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