get_host_status

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

With no annotations, the description carries full burden. It states the output includes specific version and diagnostics info but does not disclose behavioral traits like read-only nature, potential errors if applied to non-Standard SKU, or any 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?

Two sentences, no wasted words. Information is front-loaded and clear.

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?

Given no output schema, the description sufficiently lists key output items but lacks details on return format, error conditions, or what 'diagnostics' encompasses. Adequate but incomplete for deeper understanding.

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 coverage is 100% with standard parameter descriptions (subscriptionId, resourceGroupName, logicAppName). The description does not add additional meaning beyond the schema, so baseline 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?

The description clearly states the tool gets host status for a Standard Logic App, listing specific details (runtime version, extension bundle version, diagnostics). This distinguishes it from sibling tools like get_run_details or get_workflow_definition, which target different aspects.

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 notes the tool is 'Only available for Standard SKU', a useful constraint, but does not provide explicit guidance on when to use this over alternative tools (e.g., get_workflow_definition for definitions or get_workflow_triggers for triggers).

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