create_summit_scavenger_v1

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Build' without explaining what happens to the scene (e.g., asset placement, existing objects), required permissions, or side effects.

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 short (one sentence), but it sacrifices crucial details about parameters and behavior. It is not optimally structured to front-load the most critical 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?

Despite having an output schema (not shown), the description fails to cover the parameter meaning or behavioral implications. For a 1-parameter creation tool, more context is needed to ensure correct invocation.

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?

The sole parameter 'clear_existing' has no description in the schema (0% coverage) and is not mentioned in the description. The agent has no semantic guidance beyond the parameter name and default value.

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 names a specific resource ('Gentes Scavenger V1') and clarifies its role as a 'pickup harvester with front loader bucket (idle/harvest).' This distinguishes it from sibling creation tools like 'create_summit_bobcat' or 'create_summit_gather_drone_v1,' though the verb 'Build' could be more precise (e.g., create asset).

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?

No guidance on when to use this tool versus other creation tools. The description does not specify prerequisites, context, or scenarios where alternatives should be chosen.

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