runtime-invoke

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

No annotations provided. Description explains the operation (invoke public static method) but does not disclose potential side effects (e.g., state changes, exceptions) or security considerations. Adequate but not rich.

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, front-loaded with purpose, no filler. Every sentence adds value with examples and alternatives.

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?

Lacks output schema and annotations. Does not describe the return value of the method invocation (e.g., if any). For a reflection tool, missing behavioral traits like permission requirements. Could be more complete.

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%—all three parameters are described in the schema. The description adds context about argument formats but does not significantly extend beyond schema. Baseline score of 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 specifies a specific verb ('invoke'), resource ('public static method on any class in Play Mode'), and lists concrete use cases. It clearly distinguishes from sibling tool 'reflection-method-call' for instance methods.

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?

Explicitly states when to use (public static methods, in Play Mode) and when not to (instance methods on MonoBehaviours, directing to 'reflection-method-call'). Provides clear context.

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