list_messaging_services

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

The description gives no information about behavioral traits such as pagination (limit/offset), filtering (fields), or the effect of the 'include_deleted' parameter. With no annotations, the agent is left unaware of the tool's operational characteristics.

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?

While the description is short, it is under-specified rather than concise. One sentence is insufficient to convey necessary information, making it inadequate for effective tool usage.

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?

The tool has four optional parameters and no output schema. The description fails to explain the return format, pagination behavior, or any other context needed for correct invocation, leaving a significant gap in understanding.

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 input schema has four parameters with titles and defaults but no descriptions. The description does not add any additional meaning or context for the parameters, resulting in zero semantic contribution beyond the schema itself.

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 'List messaging services' uses a verb and resource, clearly indicating the action. However, it is essentially a restatement of the tool name, providing no additional context to distinguish it from other list tools beyond the resource name.

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 provided on when to use this tool versus alternatives like 'get_messaging_service' or other list tools. The description does not mention any conditions, prerequisites, or comparisons.

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