ise_ers_create

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether create is destructive/hazardous, whether it overwrites existing resources, what error conditions occur (e.g., duplicate resource names), or what the response format looks like. For a create/mutation operation with zero annotation coverage, this is a significant gap.

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 concise sentences with useful cross-references to ise_ers_get and the deployment listing tool. The description is efficient with no wasted words, though it could be structured slightly better by separating the main action from the guidance.

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?

There is no output schema, so the description would need to explain return values, but it doesn't. The tool has a large enum of 70+ resource types and nested object parameters, making it complex. The description points to ise_ers_get for an example and acknowledges the data must match the resource schema, which partially compensates for the complexity, but a mutation tool with no annotations and no output schema should convey more about outcomes and risks.

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 100%, so all three parameters (data, resource, deployment) are documented in the schema. The description adds the helpful hint to provide JSON matching the resource schema, but otherwise the parameters are well-covered by the schema's own descriptions. Baseline 3 is appropriate.

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 uses a specific verb+resource pattern: 'Create a new ERS object', which clearly states the action. It distinguishes from update/patch/delete siblings via the 'Create' verb, though it doesn't explicitly name the alternatives. The purpose is clear but relies on the tool name and sibling context rather than spelling out 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?

The description advises to use ise_ers_get first to see an example payload, which is useful guidance for the create flow. However, it doesn't explicitly state when NOT to use this tool or name alternatives (ise_openapi_* create tools). The deployment parameter references ise_list_deployments, but overall when-to-use guidance is implied rather than explicit.

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