gsa_output_data_exist

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about permissions, side effects, or error behavior. The only implicit trait is that it is a read-only existence check, which is left for the agent to assume.

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?

A single short sentence with no padding, so nothing is wasted, but the brevity reflects under-specification rather than economy of 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?

An output schema exists, so return-value explanation is not required, but the description omits the identifier's meaning, the initialization precondition, and any behavioral context. For a check tool whose result gates other operations, this is too thin.

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 0% and the single parameter entity_id is undocumented in the schema. The description's only attempt is 'for id', which does not clarify what kind of entity id this is (e.g. load case, member, element) or the expected value domain.

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 check (existence of initialized output data) but largely restates the tool name 'gsa_output_data_exist'. The phrase 'for id' is too vague to distinguish which identifier is involved, and no sibling such as gsa_output_init or gsa_case_results_exist is referenced.

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?

There is no guidance on when to call this check, what precondition (e.g. output must have been initialized via gsa_output_init) makes it meaningful, or how it relates to alternatives like gsa_case_results_exist. Usage must be inferred entirely.

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