create_style

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states this is a creation operation, it doesn't mention permissions required, whether the style becomes immediately available, what happens on duplicate names, or any rate limits. The return format is mentioned but lacks detail about what 'status and style information' includes.

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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value, though the Returns section could be more specific about what information is included. The structure helps with quick scanning.

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 creation tool with 3 parameters, no annotations, and no output schema, the description provides adequate basics but lacks important context. It covers the purpose and parameters reasonably well but misses behavioral details like error conditions, authentication requirements, and specific return format that would be needed for reliable tool invocation.

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?

With 0% schema description coverage, the description compensates well by explaining all three parameters: 'name' for the style name, 'sld' for XML content, and 'workspace' as optional. It clarifies that workspace is optional and provides context about what each parameter represents, though it doesn't specify format constraints for the SLD XML.

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 clearly states the specific action ('Create a new SLD style'), resource ('in GeoServer'), and technology context ('SLD style'). It distinguishes from siblings like create_layer or create_workspace by specifying it creates a style rather than other GeoServer resources.

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 provides no guidance on when to use this tool versus alternatives. While it's clear this creates styles, there's no mention of when to create a style versus using existing ones, or how this relates to sibling tools like create_layer or generate_map that might involve styling.

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