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

Annotations already mark it read-only and idempotent; the description adds what is actually returned (AMKO pods in avi-system followed by the GSLBConfig YAML if present) and the reliance on the current kubectl context. This behavior is disclosed beyond the structured hints, though it omits possible failure modes.

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?

Three sentences front-load the purpose, then give the return payload and usage routing. Every sentence contributes information; there is no filler or repetition of schema data.

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?

For a zero-parameter read-only tool with an output schema and rich sibling context, this description is complete: it states what is returned, when to use it, and the context caveat. No additional guidance is needed for 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 tool has zero parameters (0% schema requirement), so the baseline is 4 and the description does not need to document inputs. The only implicit input, the current kubectl context, is called out explicitly.

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?

Starts with '[READ]' and names the exact resource: AMKO (AVI Multi-Cluster Kubernetes Operator) GSLB status. It specifies the action (returns status) and differentiates from the single-cluster ako_status sibling, so an agent can select it correctly.

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?

Explicitly says 'Use this only for multi-cluster GSLB questions' and directs the agent to ako_status for single-cluster AKO health. It also cautions that the tool always reads the current kubectl context, with a pointer to ako_clusters.

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

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

Annotations already mark it read-only and idempotent, and the description adds important behavioral detail beyond that: every context is probed, kubectl must be on PATH, and unreachable clusters cause latency. It also clarifies the AKO Status values ('pod phase or Not deployed') and that Version is returned per context.

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?

Three concise, front-loaded sentences cover purpose, return values, prerequisites, side effects, and routing to sibling tools. No sentence is wasted and the '[READ]' prefix immediately signals the operation type.

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?

For a zero-parameter discovery tool, the description is complete: it explains what is returned, what is required to run it, what behavioral caveat exists, and how to proceed next. The presence of an output schema reduces the need to describe return structures further.

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 100% schema coverage, so the baseline of 4 applies. The description adds no param-specific meaning, but none is needed because the input schema is empty and the call requires no arguments.

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 ('List') and resource ('every Kubernetes context in the active kubeconfig') and clarifies the output includes AKO deployment status. The 'Start here' phrase and mentions of sibling tools like ako_status define its distinct role among the many AKO-related tools.

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?

It explicitly says to use this tool first to get context names, then pass one to ako_status, ako_logs, or ako_ingress_diagnose. It also gives practical usage conditions: requires kubectl on PATH and warns that unreachable clusters add latency.

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

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

The description adds behavior beyond annotations: redacted credentials, empty output semantics, and non-deterministic output when chart_version is empty due to moving latest. These are operational details an agent needs to interpret results correctly and do not contradict the read-only/idempotent effect annotations.

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 dense but every sentence carries necessary information: purpose, output semantics, redaction caveat, relationship to upgrade, and the version-pinning caveat. It is front-loaded with purpose and avoids filler.

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 the one optional parameter, the read-only annotations, and the presence of an output schema, the description covers usage timing, output interpretation, credential masking, and the non-determinism caveat. Nothing essential is missing for selecting and invoking this tool.

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% and the schema already documents chart_version, so the baseline is 3. The description adds value by explaining the practical effect of an empty value: the registry's moving latest is resolved and two runs can differ, plus the recommendation to pin using ako_version.

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 opens with the marker '[READ]' and states a specific verb+resource: 'Pending Helm value changes that have not been applied yet,' then clarifies it returns 'helm's diff output.' This distinguishes it from read/show tools (ako_config_show) and aligns with the diff/upgrade family.

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?

It gives explicit usage context: use before ako_config_upgrade, and says both run 'the same command,' so the preview is real. It also instructs the agent to read ako_version and pass it when chart_version is empty, providing a concrete safe invocation path.

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable behavior beyond that: it returns YAML as Helm reports it and explicitly notes that chart defaults are excluded, which is useful and not redundant with the annotations.

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?

Every sentence earns its place: the [READ] marker, the resource and content summary, the output format, the usage order, the alternative tool, and the critical install-time-only caveat are all packed into three tight sentences. No fluff.

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?

For a no-parameter read-only tool with a rich annotation set and an output schema, the description fully covers what an agent needs: what it returns, how to invoke it first, when to choose the sibling, and a key data limitation. Nothing important is missing.

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, so per the rubric the baseline is 4. There is no parameter ambiguity, and the schema is fully covered vacuously. The description appropriately focuses on behavior instead of parameter details.

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?

Description states a clear verb ('read') and specific resource ('AKO Helm release's values'), with examples such as controller IP, cloud name, and network settings. It is clearly distinguished from the sibling ako_config_diff, which reads as a comparison tool for upgrades.

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?

Explicit guidance says 'Use this first to read the live config' and directs the agent to ako_config_diff instead 'to see what an upgrade would change.' It also clarifies the limitation that only install-time values appear, not chart defaults, which helps set expectations.

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

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

Annotations only mark this as a non-read operation; the description adds substantial behavior: dry_run defaults to true, output credentials are redacted, the avi-system release is found automatically, the Broadcom OCI chart is upgraded with --reuse-values, and confirmed gates the real upgrade. No contradiction with annotations.

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 compact, front-loaded with purpose and default behavior, and each sentence adds needed context: what it does, what output looks like, the recommended prior step, and the safety gate. No filler or redundancy.

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?

With an output schema present and all parameters fully described in the schema, the description covers the remaining essential context: safety mode, prerequisite diff, automatic release discovery, and redaction behavior. Nothing critical is missing for an agent to call this tool correctly.

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%, including defaults and cross-parameter behavior for confirmed and dry_run. The description reinforces the key gate "applying (dry_run=False) requires confirmed=True" but does not add much beyond what the schema already documents.

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 opens with "[WRITE] Apply an AKO Helm upgrade," which states a specific verb, resource, and action. It further clarifies the default dry-run behavior and distinguishes the tool from read-only siblings like ako_config_diff by framing it as the applying step.

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?

It explicitly tells the agent to run ako_config_diff first to review the change, creating a clear workflow. The SAFETY line explains when preview-only vs actual applying occurs: applying requires confirmed=True. It does not explicitly name alternative tools for other situations, but the prerequisite and gating conditions are clear.

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

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

Annotations already convey readOnly, idempotent, and non-destructive behavior, so the description does not need to repeat those. It adds genuinely useful behavioral detail beyond annotations: TLS checks are skipped when secrets cannot be listed, and results are per-Ingress with OK/ISSUES status.

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 compact and front-loaded: purpose first, then return content, then usage routing, then scope and edge-case behavior. Every sentence adds value, with no filler or repetition of schema content.

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?

For a read-only diagnostic tool with an output schema, the description covers all essential information: what is validated, what is returned, which sibling tool to use for single-Ingress analysis, prerequisite tooling, namespace scope, and a known edge case.

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 100%, with both namespace and context already documented. The description adds no parameter-level detail beyond the schema, which is acceptable because the schema carries the full burden.

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 a specific verb ('Validate') and precisely defines the resource and scope: every Ingress in one namespace, checking IngressClass and TLS secret references that would block AKO from creating a Virtual Service. It also distinguishes itself from the sibling tool ako_ingress_diagnose by clarifying it handles all Ingresses rather than one.

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 explicit routing guidance: run ako_ingress_map first for namespace names and use ako_ingress_diagnose instead for a single named Ingress. It also sets clear scope expectations ('Covers one namespace only') and notes the TLS-check limitation when secrets cannot be listed.

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

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

Annotations already establish read-only/idempotent/non-destructive, and the description reinforces with 'Checks configuration only'. It additionally discloses validation targets and output shape, with no hidden 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?

Three compact sentences front-load the core diagnostic purpose, then add validation scope, output, and routing to siblings. No filler.

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?

Between annotations, 100% schema coverage, and output schema, the description fills the remaining gaps: diagnostic scope, output content, and next-step tools. An agent can invoke it correctly without further inference.

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 covers all three parameters with descriptions, so description need not repeat them. It only broadly references validated resources and doesn't add parameter-specific semantics beyond schema.

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?

States a specific diagnostic action on a single Ingress resource ('no corresponding AVI Virtual Service') and lists what it validates. The [READ] prefix and focus on causes/issues distinguish it from map/logs 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?

Explicitly sequences the tool: run ako_ingress_map first to identify affected Ingresses, and fall back to ako_logs/ako_sync_status when config is clean. This provides a clear decision path and alternatives.

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the '[READ]' marker adds little. However, the description adds meaningful context beyond annotations: it returns only the K8s-side perspective, not controller-side state, and explicitly scopes the inventory to all namespaces. This helps the agent understand what the operation does and does not cover.

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 compact and front-loaded with '[READ]' and the primary purpose. Every sentence earns its place: one states scope and output, one gives the follow-up workflow, and one clarifies the boundary against a sibling tool. There is no extraneous text.

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 the low complexity, single optional parameter, existing output schema, and rich annotations, the description provides everything an agent needs to select and invoke this tool correctly. It states the target resource, the returned fields, the follow-up tools, and the exclusion for missing Controller objects.

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 schema already documents the single parameter 'context' as 'K8s context name (optional)' with 100% coverage. The description adds no additional parameter detail, so the baseline of 3 applies; it neither clarifies nor obscures the parameter semantics.

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 verb ('Inventory'), a clear resource ('Kubernetes Ingresses'), and a scope ('across all namespaces'). It also differentiates itself from siblings by stating this returns Namespace, Ingress name, Host(s), and IngressClass, and by referring to ako_ingress_check, ako_ingress_diagnose, and ako_sync_diff as alternatives for different steps.

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 explicitly says to start here for namespace and Ingress names, then pass them to ako_ingress_check or ako_ingress_diagnose. It also states the boundary: 'Lists the K8s side only' and directs the agent to use ako_sync_diff for Ingresses with no Controller object, making when-to-use and when-not-to-use clear.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: 'Returns raw log text, not a table' and 'Only the running container's logs are returned,' which alerts the agent to output format and scope limitations. No contradiction with annotations.

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 three short, purposeful sentences. It front-loads the tool's purpose, states the return format, gives usage triggers, and notes a scope limitation. Every sentence earns its place with no filler.

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?

For a read-only log retrieval tool, the description covers purpose, trigger conditions, return format, and container scope. Combined with rich annotations, a full parameter schema, and an output schema, nothing essential is missing for an agent to select and invoke this tool correctly.

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 100%, so the parameter meanings are already fully documented. The description does not add parameter-specific guidance (e.g., how tail/since/context interact), but because the schema covers all parameters with defaults and examples, 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 opens with '[READ] AKO pod logs' and specifies concrete use cases: 'Ingress creation failures, sync errors, Controller connectivity.' It also distinguishes the tool from table-returning siblings by stating 'Returns raw log text, not a table,' so an agent can disambiguate from tools like vs_error_logs or ako_status.

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 explicit trigger conditions: 'Use when ako_status shows the pod unhealthy or ako_sync_diff reports a missing Ingress.' This names sibling tools as decision points and provides clear context. However, it does not state when not to use this tool or name alternatives beyond the implied conditions.

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

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

Beyond the destructiveHint annotation, the description discloses the deletion-and-recreation mechanism, preview behavior without confirmed=True, possibility of traffic disruption, and expected post-restart workflow. This is strong behavioral transparency that matches and enriches the annotations.

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 compact, front-loaded with the core action, and organized into clear sections: action, result, use cases, follow-up, and safety. Every sentence adds value with no wasted words.

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?

For a destructive restart tool with annotations and schema coverage, the description supplies all needed context: how the restart works, what changes require confirmation, what side effects occur, and what to do next. No critical operational detail is missing.

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%, so baseline is 3. The description adds meaningful semantics for the confirmed parameter: false returns a preview and changes nothing, while true deletes the pod and triggers recreation. This goes beyond the schema description.

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 action: restarting the AKO pod by deleting it, with the StatefulSet recreating it. This verb-object-resource structure is specific and distinguishes it from sibling AKO tools like ako_status and ako_logs.

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 explicit use cases ('Use when AKO is stuck or after config changes') and prescribes follow-ups (run ako_status, then ako_logs if not Running). It does not provide explicit when-not-to-use guidance or alternatives, so it stops just short of a 5.

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

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

The annotations already cover read-only, idempotent, and non-destructive behavior, so the description doesn't need to restate those. It adds useful behavioral context beyond annotations: the tool checks only one context's AKO namespace, returns specific status fields, and is designed as the first diagnostic step. This gives the agent a clearer picture of operational behavior without over-explaining.

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 compact yet information-dense: every sentence earns its place. It front-loads the core purpose and read-only marker, then delivers output details, usage context, and fallback guidance without repetition or filler. The structure moves from 'what' to 'when' to 'what's next', which is easy for an agent to parse.

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?

For a tool with one optional parameter and a single narrow purpose, the description is fully sufficient. It covers the expected inputs, outputs, scope limitation, and next-step tools, and an output schema is already available for return-value details. Nothing an agent needs to select and invoke this tool correctly is missing.

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% since the single optional 'context' parameter is already documented as 'K8s context name (optional, uses current context)'. The description adds some relevant scope nuance by saying the tool 'Looks in one context's AKO namespace only', but it does not materially expand on the parameter's format or default behavior. A baseline of 3 is appropriate here as the schema already carries the parameter meaning.

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 opens with a clear action: 'Check AKO pod status in Kubernetes', and it names the concrete resource (AKO pod) and what is returned (pod name, phase, ready flag, restart count, namespace). It also distinguishes itself from related AKO tools by positioning itself as the 'First step for Ingress or LoadBalancer issues' and pointing to ako_logs and ako_clusters as follow-ups. This is a specific, well-scoped purpose with no ambiguity.

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 explicitly says when to use this tool ('First step for Ingress or LoadBalancer issues') and what to do afterward ('follow with ako_logs when it is not Running'). It also explains a boundary case: 'Looks in one context's AKO namespace only — run ako_clusters if not found.' This gives the agent clear routing to alternatives without leaving it to inference.

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

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context: the heuristic shard-mode matching, the need to confirm 'Missing' results, and the output shape (Type, namespace/name, Status). No contradiction with annotations.

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?

Three dense sentences: purpose first, return value second, usage and caveat third. No filler or repeated schema information. Every sentence earns 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?

For a tool with one optional parameter, strong annotations, an output schema, and explicit sibling context, this description fully equips an agent to select and invoke it correctly, including a critical heuristic-matching caveat.

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% for the single optional context parameter, so the baseline of 3 applies. The description does not elaborate on the parameter, but it does not need to because the schema already provides a clear description and default.

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?

States a specific verb and resource: 'List Ingresses with no matching Virtual Service or pool on the Controller.' This clearly distinguishes it from the sibling tools ako_sync_status and ako_sync_force by focusing on diff detection.

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?

Explicitly says when to use it ('Use when ako_sync_status reports a mismatch'), names the reconciliatory alternative (ako_sync_force), and directs confirmation of shard-mode results via pool_list. This gives an agent unambiguous routing criteria.

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

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

Annotations already mark this destructive and non-read-only, but the description adds concrete consequences: brief traffic disruption, a preview-only mode unless confirmed=true, and a one-line result. It does not contradict annotations and adds safety-relevant behavior beyond the flags.

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 compact and front-loaded: core action first, then result type, usage trigger, safety warning, and required confirmation. Every sentence contributes either use-case guidance or a behavioral warning.

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?

For a destructive resync tool with annotations, a rich confirmed parameter description, and an output schema, this definition gives all essential context: what it does, when to use it, what to run first, and the safety gate. No necessary operational detail is missing.

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%, and the confirmed parameter already explains the default preview behavior and the restart/rebuild consequence. The tool description reinforces the confirmed requirement but adds no new meaning beyond the schema's parameter descriptions.

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 opens with '[WRITE] Force AKO to resync all K8s resources with the AVI Controller', naming a specific verb, resource, and effect. It also positions the tool against siblings by referencing ako_sync_diff and ako_sync_status, so an agent can tell it apart.

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?

It explicitly says to use when drift is detected, warns of brief traffic disruption, and instructs running ako_sync_diff first to inspect out-of-sync state. It also states the safety gate: confirmed=true is required, and without it only a preview is returned.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds meaningful behavioral nuance: this is a cheap preliminary count comparison, not a full diff, and shard mode can produce false mismatches. It also states exactly what the tool returns, going beyond the structured safety hints without contradicting them.

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 three sentences, each earning its place: the operation and resources, the returned verdict, and the critical usage caveat. It is front-loaded with the purpose and avoids any filler or redundant restatement of the tool name.

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?

For a tool with one optional parameter, rich annotations, an existing output schema, and clear sibling guidance, this description is complete. It tells the agent what the tool does, what it returns, when to use it as a first check, and what caveat to keep in mind—nothing needed for correct invocation is missing.

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?

There is only one optional context parameter, and the input schema already describes it as 'K8s context name (optional)' with 100% coverage. The description adds no further parameter detail, but none is needed since the schema fully documents the parameter.

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 verb ('Compare') and two concrete resources (K8s Ingresses and AVI Virtual Services), and states the output (counts plus a match/mismatch verdict). It also distinguishes itself from the sibling ako_sync_diff by noting the latter identifies which objects differ, so an agent can tell them apart.

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?

It gives explicit usage direction: 'Use this first as a cheap check, then ako_sync_diff for which objects differ.' It also sets expectations by explaining the comparison is count-only and that a mismatch is not necessarily a problem in AKO shard mode, which prevents the agent from over-trusting the result.

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

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the description adds meaningful context beyond them: the version source is the pod's image tag, and the edge case that 'latest' is reported literally rather than resolved to a numeric version. This gives the agent an accurate mental model of the tool's behavior.

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 tight and front-loaded: the action and source appear in the first line, followed by output shape, use cases, and a critical caveat. Every sentence earns its place and there is no redundant elaboration.

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, the description covers the essential non-schema context: what the version is derived from, the returned fields, the use-before-config workflows, and the 'latest' ambiguity. For a simple read-only tool with one optional parameter, nothing needed for correct invocation is missing.

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, context, is fully documented in the schema as the optional K8s context name (100% coverage). With coverage that high, the description does not need to add parameter detail, and it does not meaningfully enrich the parameter's semantics beyond the schema.

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?

Description leads with a specific verb and resource: '[READ] AKO version running in a cluster, read from the pod's image tag.' It clearly defines the output (pod name and Image/Version pair per container) and distinguishes the tool from siblings by framing it as a foundational compatibility check referenced by ako_config_diff and ako_config_upgrade.

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?

Explicitly states when to use: to check Controller compatibility and before running ako_config_diff or ako_config_upgrade so both target the installed chart. It gives concrete usage triggers but does not explicitly mention when not to use this tool or name a direct alternative for version queries.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the read-only nature is covered. The description adds a domain caveat about pool naming that helps interpret results, plus '[READ]' reinforces the safety profile. No contradiction.

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?

Three short sentences, front-loaded with purpose, then return fields and usage. Every sentence adds information and there is no redundancy with the schema.

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?

For a read-only list tool with one optional parameter, a full output schema, and rich annotations, the description covers purpose, expected results, and sequencing relative to pool_members. Nothing else is needed for 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?

Schema description coverage is 100%; vs_filter is fully described with substring matching semantics and default behavior. The description adds no parameter-level details beyond that, so the schema carries the burden.

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?

States a specific action ('Discover pools') and a resource ('Controller'), then enumerates the exact fields returned (Name, member count, Enabled, short UUID). The contrast with sibling pool_members makes distinguishing easy.

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?

Explicitly directs the agent to call this before pool_members and gives the reason (pool names often differ from VS names). This is a clear when and names the alternative, so no inference is needed.

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

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses the graceful drain behavior, the one-line return result, and the safe preview mode when confirmed is not true. It clearly explains the destructive action and its confirmation requirement without contradicting annotations.

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 compact and front-loaded: purpose and effect first, then usage guidance, then safety. Every sentence adds distinct value, with no filler or redundancy.

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 description covers the action's purpose, usage context, prerequisites, reversal command, return style, and safety confirmation. With an output schema and complete parameter schema present, no essential information is missing for the agent to call this tool correctly.

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 100% and each parameter already has detailed semantics, including confirmed's preview vs. actual disable behavior. The description adds little parameter-level detail beyond reinforcing the confirmed=True safety requirement, which is already present in the schema.

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 and resource: 'Disable a pool member with graceful drain' and immediately explains the behavioral effect: existing connections complete, no new traffic. It clearly distinguishes from the sibling pool_member_enable by noting it reverses the action.

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 explicit usage context: 'Use for maintenance or rolling deployments' and instructs the agent to 'run pool_members first for the server IP' and use 'pool_member_enable to reverse it.' This tells the agent both when to use the tool and what to do before/after.

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

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

The description discloses the return format ('one-line confirmation'), marks the operation as [WRITE], and clarifies that no membership addition occurs. These details go beyond what the annotations alone convey. It does not contradict the annotations.

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?

Three short sentences: the action and outcome are first, followed by return format and a necessary precondition. There is no redundant wording or filler.

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, both parameters are required and fully described in the schema, an output schema exists, and the description covers the key behavioral nuance. An agent has enough information to call it correctly.

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 100%, so the schema already explains that pool must be an exact literal name and server is an IP address. The description adds the practical note to verify via pool_members, but does not substantially expand parameter meaning beyond the schema.

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 a specific verb and resource: 'Enable a pool member so it receives traffic again.' This clearly differentiates it from pool_member_disable and states the intended effect. The [WRITE] prefix reinforces the action type.

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?

It explicitly instructs to 'Use pool_members first to verify the server IP' and states that 'The server must already belong to the pool — this adds nothing.' This gives useful context and a precondition, though it does not explicitly mention the sibling pool_member_disable as the inverse alternative.

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

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds a valuable behavioral caveat: it reflects configured state, not live health-monitor results. It also discloses exactly which output fields are returned. No contradiction with the annotations exists.

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 compact and front-loaded: the action and result fields come first, followed by workflow context and a caveat. Every sentence earns its place, with no filler or repeated schema 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?

For a read-only, single-parameter listing tool with an output schema, the description fully covers what it returns, prerequisites, sibling-tool relationships, and an important limitation. Nothing an agent needs to decide when or how to call it is missing.

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%, and the pool parameter is already richly documented in the schema with exact-match semantics, literal matching, and a warning not to infer the pool name from a Virtual Service name. The description only reinforces this by saying to run pool_list first, so it adds little beyond the schema.

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?

Description starts with a clear action and object: 'List the members of a pool.' It also names the specific returned fields (Server IP, Port, Enabled, Ratio), and the '[READ]' prefix reinforces its read-only nature. The tool is distinguished from siblings by explicitly positioning it relative to pool_member_enable/pool_member_disable and pool_list.

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?

It gives explicit workflow guidance: 'Use before pool_member_enable or pool_member_disable' and 'run pool_list first for the pool name.' It also states an exclusion — 'Reports configured state only, not live health-monitor results' — so an agent knows when not to rely on this tool.

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

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

Annotations already establish the read-only, idempotent, non-destructive profile, so the description's '[READ]' tag adds a little. More valuable is the explicit edge case that an SE with no VS reports 0 rather than an error, which is useful behavioral context beyond the structured annotations.

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 compact and well-structured: purpose is front-loaded, followed by return fields, usage guidance, alternatives, and a critical edge case. Every sentence contributes information an agent needs.

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?

With no parameters, an output schema present, and comprehensive annotations, the description covers the remaining practical concerns: what fields are returned, when to use the tool, and the zero-VS reporting behavior. Nothing an agent needs to invoke or interpret the result is missing.

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 takes zero parameters, so the description does not need to explain any. Per the calibration, zero param count starts at baseline 4, and the description correctly avoids inventing parameter details.

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 reports the health of every Service Engine, including name, operational status, and VS counts. It also distinguishes itself from related tools like se_list and vs_status, so an agent can identify its role without ambiguity.

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 explicitly says when to use this tool: when VS health degrades and the agent needs to determine whether the issue is at the SE level. It also names se_list and vs_status as alternatives and explains what each provides, making the routing decision clear.

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

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by stating the call cannot be paged or filtered and enumerates what it returns, going beyond the annotation signal.

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 compact, front-loaded with the [READ] intent, and each sentence adds meaningful information. There is no fluff or repetition.

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?

For a zero-parameter read-only list operation with an output schema present, the description covers the purpose, usage, limitations, and alternative. Nothing essential is missing for an agent to invoke it correctly.

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 takes zero parameters, so the baseline is 4. The description adds no parameter details because none are needed; it instead explains the output fields and constraints.

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 verb and resource ('List Service Engines ... on the Controller') and states the returned fields. It also differentiates this tool from se_health by noting the health-focused sibling.

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?

It gives explicit use cases ('inventory capacity or find an SE's name and IP') and explicitly directs the agent to se_health for degraded VS health. This provides clear when-to-use and when-not-to-use guidance.

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

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description adds genuine result behavior on top: soonest-first ordering and the edge case that 'Expired certs are included, with negative days remaining.' This goes beyond what the annotations disclose, though it stops short of covering pagination or rate limits, which are likely non-issues for a filtered read tool.

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?

Three sentences, each earning its place: purpose, return contract, and sibling routing. The '[READ]' prefix and 'soonest first' flag are efficient front-loaded signals with zero filler.

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?

For a one-optional-parameter read tool with an output schema and safety annotations, the description covers the return fields, ordering, default behavior, edge case (expired certs), and the alternative tool. Nothing an agent needs to invoke it correctly is missing.

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%: the schema already documents 'days' with a description and default of 30. The tool description repeats the default ('within N days (default 30)') but adds no meaning beyond the schema, so the baseline of 3 is correct.

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 verb ('Check') and resource ('SSL certificates expire within N days'), and immediately distinguishes itself from siblings: 'Use this instead of ssl_list when you only want certificates near expiry.' An agent can tell this apart from the 28 sibling tools without opening schemas.

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?

It explicitly names the alternative (ssl_list) and gives the selection condition ('when you only want certificates near expiry'), which implies the inverse condition for the sibling. This is exactly the explicit when/alternative guidance the rubric rewards.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context beyond annotations: the call "cannot be paged or filtered" and returns specific fields. The [READ] prefix reinforces the non-mutating nature.

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 three tight sentences with no filler. The main purpose is front-loaded, followed by the return fields, the key limitation, and the sibling alternative. Every sentence adds distinct value.

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?

For a zero-parameter read-only list tool with an output schema, the description is complete: it names the resource, states the returned fields, notes the pagination/filtering limitation, and directs the agent to the appropriate alternative. Nothing an agent needs to call it correctly is missing.

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, so there are no parameter semantics for the description to clarify. The description adds that the call is unfilterable, which implicitly confirms that no filtering parameters exist. The baseline for zero-parameter tools is 4, and no deductions are warranted.

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 opens with a specific verb and resource: "List SSL/TLS certificates stored on the AVI Controller." It clearly distinguishes the tool from the sibling ssl_expiry_check by stating that this one is for inventory or exact name lookup while the sibling is for certificates expiring soon.

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 explicitly says when to use this tool: "Use for inventory or a certificate's exact name — use ssl_expiry_check instead for only the ones expiring soon." This provides both a positive use case and an explicit alternative, leaving no ambiguity about selection.

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

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

Annotations already declare readOnly, openWorld, and idempotent behavior, and the description adds valuable context beyond them: the fixed 12-sample/5-minute window that cannot be changed, and the non-obvious empty-output semantics meaning no traffic rather than an error. This fully informs the agent of behavioral edge cases.

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?

Four short sentences each earn their place: the purpose, the metric/window detail, the empty-output signal, and the usage guidance. It is front-loaded and has no filler.

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?

For a single-parameter read-only tool with a full output schema, the description is complete. It covers what the tool returns, the fixed time window, empty result behavior, and when to choose this tool versus its sibling.

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 100%, so the schema already fully documents vs_name as an exact, case-sensitive Virtual Service name from vs_list. The description adds no meaning for the parameter beyond the schema, so the baseline of 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?

States a specific action and resource: returns performance metrics for one Virtual Service over the last hour. It differentiates itself from siblings by specifying L4 and L7 metric categories, making it clear this is the analytics tool rather than vs_status or vs_error_logs.

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?

Explicitly instructs when to use this tool: when vs_status shows degraded health. It also names the alternative for per-request detail (vs_error_logs), giving the agent clear routing guidance.

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

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description adds complementary context: the 50-line limit, status >=400 filter, the exact returned fields, and the ambiguity of empty results (no errors vs capture disabled). No contradiction with annotations.

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?

Four short sentences, each earning its place. The READ intent is front-loaded, followed by return details, sibling distinction, and an important caveat about empty results. Zero wasteful wording.

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 fields are further specified there. The description covers the critical operational details: scope, result cap, status filter, alternative tool, and the empty-result ambiguity. Nothing an agent needs to correctly invoke or interpret the tool is missing.

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 100%, so both parameters are fully documented in the schema; the description adds no additional parameter semantics beyond the general purpose of the tool. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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?

States a specific verb, resource, and scope: 'Returns... error logs for one Virtual Service' with explicit detail on line limit, status threshold, and fields. It directly names the alternative vs_analytics, so an agent can distinguish without opening either schema.

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?

Explicitly says 'Use this instead of vs_analytics for per-request detail', naming the alternative and the condition that selects this tool. It also adds interpretation guidance for empty results, which helps decide whether to escalate or check configuration.

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

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

The annotations already declare the tool read-only, idempotent, and non-destructive, but the description adds operational behavior beyond that: it returns every VS in one call, cannot be paged or filtered, and intentionally omits health scores. This is exactly the contextual disclosure an agent needs to invoke it correctly.

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?

Every sentence earns its place: a clear purpose, a compact summary of returned data and limitations, and an explicit next-step recommendation. The information is front-loaded and there is no filler.

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?

For a simple read-only list tool with one optional parameter, an output schema, and a clear sibling relationship, this description is complete. It covers return contents, the all-at-once nature, limitations, and the recommended follow-up tool, so an agent can choose and call it correctly without opening the schema.

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 only parameter, 'controller', is fully described in the input schema with its default and meaning. Schema description coverage is 100%, so the description does not need to repeat parameter details. The baseline 3 applies since no additional parameter-level nuance is provided.

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 opens with a specific verb and resource: 'List Virtual Services on the AVI Controller.' It then enumerates the returned fields (Name, Enabled, VIP, short UUID), so an agent knows precisely what this tool does. It also distinguishes itself from vs_status via the final sentence.

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 explicitly places this tool in a workflow: 'Use this before drilling into one VS with vs_status.' It also states the key limitations—no pagination, no filtering, no health score—so an agent knows when not to rely on it and can route to the more specific sibling.

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

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral specifics beyond annotations: exact-name matching is required, a mismatch fails, and the response is one detail block, not a list. No contradiction with annotations.

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 compact and front-loaded with the [READ] marker and the key purpose. Every sentence contributes either core semantics, a failure condition, or routing to alternatives, with no filler or repetition.

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?

For a single-parameter read tool with a rich output schema and strong annotations, this description is complete. It covers prerequisite ordering, exact-match failure, the shape of the return (one block), and sibling tool routing, so an agent has everything needed to invoke it correctly.

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% and the name parameter already has the description 'Exact Virtual Service name.' The tool description reinforces the exact-match requirement, but adds no new parameter format or syntax details beyond what the schema provides, 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?

Description clearly states the tool's function: detailed status for one Virtual Service including VIP, pool, health, connections, and throughput. It differentiates from siblings by noting it returns a single detail block rather than a list, and specifies that vs_analytics and vs_error_logs serve complementary purposes.

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?

Explicitly tells the agent to call vs_list first to obtain an exact name, warns that a non-exact name fails, and directs metrics to vs_analytics and 5xx to vs_error_logs. This is clear when-to-use and when-not-to-use guidance beyond what annotations provide.

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

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

The description adds safety-critical behavior beyond the destructiveHint annotation: disabling stops all traffic, an unconfirmed disable is preview-only and changes nothing, confirmed=True is required to actually disable, and enabling always executes. It also discloses the one-line result format.

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 compact and front-loaded: purpose, then result, then prerequisite, then safety. Every sentence contributes essential selection or invocation guidance without filler.

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?

For a destructive, non-idempotent tool, the description covers purpose, effect, prerequisite check, result shape, and the critical confirmation gate. Combined with the fully-documented schema and output schema, an agent has enough to invoke it correctly and safely.

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 input schema already provides 100% coverage for all three parameters, including the confirmed flag semantics. The description reinforces that confirmed gates only disable and is ignored for enable, but does not add substantial new meaning beyond the schema.

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 the specific action ('Enable or disable a Virtual Service') and the concrete effect ('Disabling stops all traffic to it'). This clearly distinguishes vs_toggle from read-only siblings like vs_status and vs_list.

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?

It explicitly directs the agent to use vs_status first to check current state, and it explains the preview-vs-execute behavior for disabling based on the confirmed flag. It does not explicitly enumerate when-not-to-use conditions, but the context is clear enough for correct selection.

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