gaea_find_install

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'Find local QuadSpinner Gaea executables' but does not specify what the tool returns (e.g., paths), whether it searches PATH, registry, or known install locations, or whether it may return multiple results. Given the lack of annotations, this is a notable transparency gap.

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 a single, direct sentence with no wasted words. It is front-loaded with the core action and resource, making it ideal for quick parsing by an AI agent.

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?

The tool is simple (no params, no output schema, no annotations), but the description does not mention what the tool returns or how the results are presented. For a 'find' operation, it is reasonable to assume paths to executables, but this is not explicit. Given the absence of an output schema, the description should clarify the return value to be fully 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?

The tool has zero parameters, and the input schema is empty with 100% schema description coverage. The baseline for zero-parameter tools is 4, and no parameter-related information is needed in the description. The description does not introduce confusion about parameters.

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 states a specific verb ('Find') and a resource ('local QuadSpinner Gaea executables'), making the tool's function immediately clear. It is distinct from all sibling tools, which focus on graph manipulation, building, and output handling. The purpose is unambiguous and actionable.

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 gives no explicit guidance on when to use this tool versus alternatives, and no sibling tool is mentioned. Usage is only implied by the tool's name and description—it would be used when the agent needs to locate Gaea executables. There is no exclusionary guidance or mention of a more appropriate sibling for related tasks.

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