h3yun_list_apps

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that applications are 'visible to the signed-in user,' implying authentication context, but it does not disclose side effects, rate limits, pagination, or any other behavioral traits. For a tool with zero annotation coverage, this is insufficient.

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 sentence that fronts the action verb 'List' and contains no filler. It is both concise and well-structured, with every word earning its place.

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 has an output schema, so return structure is handled separately. The description covers the core function and user context, but it lacks explicit guidance on choosing this tool over alternatives and omits notes on pagination or limits. It is minimally adequate for a zero-parameter tool but leaves room for improvement.

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 no parameters, so the schema is completely covered (empty). The baseline is 4, and the description adds meaningful context by indicating that results are filtered by the signed-in user's visibility, which enriches the semantic meaning beyond the empty schema. No deduction needed.

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 uses the specific verb 'List' with the resource 'applications' and scopes it to 'visible to the signed-in user.' This clearly differentiates it from siblings like h3yun_list_forms by the object type, though it does not explicitly name alternatives. It is close to a 5 but stops short of naming competing siblings.

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 provides no guidance on when to use this tool versus its siblings (e.g., h3yun_list_forms or h3yun_search_forms). It simply states what it does without any mention of alternatives, exclusions, or contextual prerequisites, leaving the agent to infer based on resource names.

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