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

With no annotations, the description carries the full behavioral burden. It does disclose a genuine trait not derivable from schema — the 160-character message limit — and indicates which credentials are required (api_key, token, wallet_fk). However, it says nothing about recipient resolution, delivery success/failure behavior, rate limits, or permissions, so disclosure is partial.

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 purpose sentence is front-loaded and useful, but the opening sentence is duplicated verbatim, wasting the most prominent position. The param/return block is terse and serviceable, though '@return: a json object' adds little.

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 five-required-param write tool with no annotations and no output schema, the description covers the basics (purpose, size limit, credentials, param meanings). It omits failure modes, whether the send is idempotent, and any detail beyond 'a json object' for the return, leaving a moderate gap.

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%, so the description must compensate, and it does document all five parameters, including provenance for token and wallet_fk ('provided by /access/login') and content types for message and title ('plain text'). wallet_fk's explanation is largely circular (restating the name), which keeps it out of the top score.

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 ('Sends a push message to customer') and adds a scoping constraint (160 characters per message). It does not name any sibling, so an agent must still infer how this differs from netfluid__email, netfluid__account_send_sms, or netfluid__push_message_devices. Clear purpose, but no sibling differentiation.

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 statement of when to use this tool versus the other messaging tools (email, send_email, account_send_sms, push_message_devices), and no prerequisites or exclusions. The 160-character note is a constraint, not usage guidance.

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