list_soap_messages

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

Annotations already declare 'readOnlyHint', 'idempotentHint', and 'openWorldHint', which communicate that the tool is safe, idempotent, and may return varying results. The description adds no further behavioral context (e.g., pagination, sorting defaults). It does not contradict annotations.

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, concise sentence with no unnecessary words. It is efficient but could benefit from more structure, such as a hint about the output.

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 list tool with full schema coverage and informative annotations, the description is minimally adequate. It lacks information about what fields the output includes, which would be helpful since there is no output schema. However, it does not miss critical details for basic usage.

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 100% coverage with clear descriptions for parameters: 'query' (search by name or endpoint), 'active' (filter by active status), 'limit' (max records). The description adds no additional meaning beyond the 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 states the action 'List' and the resource 'outbound SOAP Message configurations' with a table hint 'sys_web_service'. It clearly indicates the tool's function and distinguishes from the sibling 'get_soap_message' which retrieves a single configuration. However, it does not explicitly differentiate it from other list tools like 'list_soap_message_functions'.

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives like 'get_soap_message' or 'search' tools. There are no prerequisites, context, or exclusions.

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