object_style

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates the operation sets values, but does not disclose side effects, file modification behavior, selection resolution semantics, or what happens with output_path. This is thin for a mutation-oriented tool.

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 front-loaded sentences: the first states the action and scope, the second adds a uniqueness claim. There is no redundancy or filler.

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 7-parameter tool with no annotations and no output schema, this description is too sparse. It does not clarify how kind maps to the two variants in practice, which parameters are needed for a valid call, or what the tool returns or modifies beyond setting a value.

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 coverage is 100%, so the baseline is 3. The description adds value by revealing the valid kind values (object-set-attribute / object-set-property) and by clarifying the scope as XML attributes and CSS properties, which enriches the otherwise terse 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 a specific action (Set) and resource (XML attribute or CSS property) on a selection, and identifies the underlying variants (object-set-attribute / object-set-property). It distinguishes this generic setter from the more specialized sibling tools like object_transform and object_filter.

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 implies this tool is for arbitrary attribute/property setting and claims uniqueness across Inkscape MCP servers, but it does not explicitly state when to prefer it over siblings or when not to use it. Context is clear enough for a generic setter, but explicit alternatives are absent.

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