set_level_properties

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

With no annotations, the description adds the partial-update behavior ('any subset') and distinguishes between level-level and hierarchy-level properties. However, it does not disclose permissions, side effects, or validation behavior, which are important for a mutation 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 concise sentences, front-loaded with the core purpose, followed by a useful exclusionary note. No redundant phrasing or unnecessary detail.

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?

The description is adequate for a simple setter, covering the main fields and pointing to set_hierarchy_properties for related settings. However, it omits return value, prerequisites, and error handling, and the required parameters are still unexplained.

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 only 43%, with just newName, ordinal, and description having descriptions. The description adds the 'any subset' semantic and explains ordinal's meaning, but does not clarify required parameters like sessionId, table, hierarchy, and level, which remain undocumented in both schema and description.

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 'Set a hierarchy LEVEL's properties (any subset): ordinal (its order within the hierarchy), description, and/or newName (rename the level).' This clearly identifies the verb, resource, and specific properties, and distinguishes it from set_hierarchy_properties for hierarchy-wide settings.

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 NOTE explicitly says 'hide-blank-members and display folder are hierarchy-wide - set those with set_hierarchy_properties,' providing a clear alternative and when-not-to-use context. It also implies this tool is for level-specific property updates.

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