editor_get_class_properties

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

With no annotations, the description is the only source of behavioral information. It implies a read-only operation via 'List' but does not state side effects, output structure, error conditions, or any constraints. This is a minimal statement without extra context.

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 concise sentence that states the core function without waste. It is appropriately front-loaded.

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?

While the tool is simple (one parameter, no output schema), the description lacks essential context: it does not specify what the returned list contains, how to format the 'class' argument, or when this tool is preferred over its many sibling introspection tools. With no annotations or output schema, this leaves significant gaps.

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?

The schema has one required parameter, 'class', with no schema-level description (0% coverage). The description only says 'of a class', which largely repeats the parameter name and does not explain expected value format, such as whether a script path, class name, or other identifier is required.

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 the specific verb 'List' and names the resource 'editor-visible properties of a class,' clearly distinguishing it from sibling tools like editor_get_class_signals or editor_get_method_list. It directly states the function.

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?

No guidance is provided about when to choose this over alternatives such as editor_get_class_signals or editor_get_method_list, nor any context for use cases. It simply states what the tool does, so the agent receives no decision support.

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