emu_post_axl_

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

There are no annotations, so the description must carry the full behavioral disclosure burden. It only says 'Accepts AXL SOAP operations,' leaving unclear whether the tool executes those operations, returns SOAP responses, creates side effects, or requires specific endpoint or authentication setup. The agent cannot anticipate what happens after a successful call.

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?

This is a single, spare sentence that front-loads the core purpose and includes concrete operation examples. There is no filler, and the description efficiently conveys what resource the tool acts upon.

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 the open schema, no output schema, and no annotations resulting in a complicated generic pass-through tool, this description is significantly under-specified. It omits the request payload format, operation parameter structure, response shape, error behavior, and any side-effect or authorization notes, so an agent cannot reliably invoke the tool correctly from this definition alone.

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 is an open object with no defined properties, and the description only lists operation names without explaining how they are encoded or what additional parameters each operation expects. Naming example operations like getPhone and executeSQLQuery gives a small amount of semantic context, but it not enough for the agent to construct a valid payload or map arguments to those operations.

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 identifies a specific resource class, 'AXL SOAP operations,' and gives concrete, recognizable examples like getPhone, getUser, listPhone, and executeSQLQuery. It is fairly clear that an agent would use this to make generic AXL SOAP calls, though 'Accepts' is less precise than 'executes' or 'sends' and it does not explicitly differentiate itself from the many other post_* siblings.

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?

The description is too small to give explicit when-to-use or when-not-to-use guidance. It implies that you should use this tool when working with AXL SOAP operations, but it does not mention alternatives, exclusions, prerequisites, or how it relates to sibling tools such as emu_get_contracts_axl or emu_query_sql.

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