unity_component_get_properties

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

No annotations provided, so description must cover behavior. It states 'serialized properties' implying non-serialized ones are excluded. No mention of read-only nature, performance impact, or error cases. Adequate but not detailed.

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?

Single sentence, no fluff. Information is front-loaded. Could optionally mention that it's read-only for transparency, but still concise.

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?

Tool is relatively simple with no output schema. Description covers purpose and key parameters. However, missing details like what exactly 'serialized properties' means, or that it might return a large amount of data. Adequate for the 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 description coverage is 100%, so baseline is 3. The port parameter description adds useful context about parallel-safe routing and referencing another tool (unity_select_instance), which provides value beyond schema.

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 verb (Get) and resource (serialized properties of a component on a GameObject). It distinguishes from sibling tools like unity_component_set_property and unity_component_get_referenceable by focusing on reading serialized 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?

Description implies use when you need to read component properties, but provides no when-not or alternative guidance. The port parameter description hints at parallel-safe routing but no explicit comparison to other component tools.

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