get_slot_properties

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

The description indicates the tool is read-only ('Read') and discloses that the return type is polymorphic based on the parent widget. However, it omits details about required permissions, error cases (e.g., widget without a slot), or side effects. No annotations exist, so the description carries full burden.

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, focused sentence that immediately conveys the action and key nuance about type dependency. It wastes no words and is front-loaded with the core purpose.

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 has an output schema (not shown), the description provides enough context for basic understanding of slot property retrieval. However, it lacks details on parameter semantics and fails to address potential complexities like handling different parent types or error scenarios.

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 input schema has 3 parameters (filter, widget_name, widget_blueprint_path) with 0% description coverage. The description does not explain any parameter, leaving the agent to infer their purpose. 'filter' is especially ambiguous without explanation.

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 tool reads layout slot properties and specifies that the slot type depends on the parent widget (e.g., CanvasPanelSlot, HorizontalBoxSlot). This distinguishes it from sibling tools like 'get_widget_properties' which read widget-level properties.

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 usage for retrieving slot-specific layout properties but does not explicitly state when to use this tool versus alternatives like 'get_widget_properties' or 'set_slot_properties'. No when-not-to-use guidance is provided.

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