get_component_properties

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

Discloses that it reads visible properties from a UI panel that requires prior user interaction. No annotations provided, so description carries the burden; it adequately conveys read-only behavior and state dependency.

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 sentences, no redundancy. First sentence states purpose, second adds critical usage condition. Highly efficient and 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?

For a simple tool with one parameter and no output schema, the description covers purpose, prerequisite, and data source. Missing details on return format or error states, but not necessary for effective use given low complexity.

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% with a clear description for componentName. Description adds no extra parameter details beyond the schema, which is acceptable; baseline 3 is appropriate.

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?

Description clearly states the tool reads property values for a component from the Properties sidebar. It distinguishes from siblings like update_component_property (write) and get_component_tree (tree structure) by specifying the action and source.

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?

Provides a clear prerequisite: the component must be clicked in the Designer first. This tells the agent when the tool can be invoked. No explicit when-not-to-use or alternatives, but guidance is sufficient for a straightforward tool.

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