get_addressables_info

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

Describes a read operation with a conditional on project setup. No annotations provided, but the simple behavior is clear. Does not disclose return format or potential empty results.

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 conveying essential information without any fluff. Perfectly 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?

Given no parameters, output schema, or nested objects, the description adequately covers the tool's purpose and condition. No missing details.

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?

No parameters present, so description naturally adds no parameter info. Baseline for zero-param tools is 4 as per guidelines.

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?

Clearly states it retrieves Addressables groups and config path, with a condition on usage of Addressables. Distinguishes from siblings by targeting a specific Unity feature.

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?

Implied usage context (when needing Addressables info) but no explicit alternatives or when-not to use. Lacks differentiation guidance from similar tools like get_ads_config.

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