ide-get-prefab-inheritance

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

No annotations are provided, so the description carries full burden. It fails to disclose behavioral traits like read-only nature (implicit but not stated), error cases, or permissions. The description only states the return type and a condition for empty arrays, which adds minimal transparency.

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 two sentences long, front-loading the core purpose in the first sentence. The second sentence explains the inheritance concept and the meaning of an empty result, which is helpful but could be more concise. No redundant information.

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 the simple tool (one parameter, no output schema), the description adequately covers the return value and the meaning of an empty array. It explains the concept of prefab inheritance. However, it lacks details on error handling or cases where the prefabId is invalid.

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 description repeats the schema's description of 'prefabId' without adding new meaning or clarifying the format. It offers no additional guidance beyond the 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?

The description clearly states that the tool returns an array of prefabs that are part of the inheritance of a given prefab, using specific verbs like 'get' and 'array'. It explains the concept of prefab variants and distinguishes itself from sibling tools like 'scene-get-nested-prefabs-instances', which deals with instances rather than inheritance.

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 does not provide any guidance on when to use this tool versus alternatives. It only describes what the tool does without mentioning contexts, prerequisites, or exclusions such as when the prefab has no variants.

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