list_modifiers

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'list' implies a read-only operation with no side effects, which is useful, but the description does not disclose ordering, error behavior, or whether only the currently selected object is affected beyond the object parameter.

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 a single short sentence with no filler. It front-loads the verb and resource, and every word contributes meaning.

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 tool is simple with one parameter and an output schema, so a brief description is mostly adequate. Still, it lacks usage differentiation from sibling tools and leaves parameter format underspecified, making it minimally viable but not complete.

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 0%, and the description only adds that the modifier stack is 'on the object', confirming that the object parameter identifies the target object. However, it does not clarify whether the value should be an object name, path, or reference, nor does it explain any format expectations for a single string parameter.

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 a specific action ('list') applied to a specific resource ('modifier stack on the object'). It is naturally distinguished from siblings like list_modifier_types (available modifier types) and get_modifier_settings (settings of a modifier) by specifying the per-object stack.

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 such as list_modifier_types, get_modifier_settings, or add_modifier. There is no explicit context, condition, or exclusion, leaving the agent to infer usage from the tool name alone.

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