ise_test_deployment

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. It discloses that probe is read-only ('read-only live connection'), spells out the exact probe actions (ERS GET + Data Connect 'SELECT 1'), and states the reporting behavior (EVERY missing field/credential at once with exact fix command). This is strong disclosure for a tool with no annotations, though it stops short of describing return format or error behaviors.

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 compact sentence that front-loads the core purpose (check config + credentials, report all missing at once) and packs behavioral detail efficiently. It's longer than a pure one-liner but every clause carries distinct information; no filler or redundancy. Could arguably be split into two sentences for readability.

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 diagnostic tool with only 2 params, no output schema, and no annotations, the description explains the trigger conditions (probe default), the side effects (read-only live connection), and the exhaustive-reporting behavior. This is reasonably complete given the tool's moderate complexity, though it doesn't describe what the output looks like (e.g., a summary of found vs missing) since there's no output 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?

Schema coverage is 100% — both parameters (probe, deployment) have descriptions in the input schema. The description adds detail to 'probe' by specifying the read-only nature and concrete probe actions, and to 'deployment' via the omit-for-default note. The description's added value over the schema is modest but real, aligning with the baseline-3 expectation for full schema coverage.

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 gives a specific verb ('Check') plus resource ('deployment's configuration and credentials'), and clearly states distinct behaviors: reporting missing fields/credentials with exact fix commands, and conditional live probe. This clearly differentiates it from siblings like ise_list_deployments (listing only), ise_add_deployment, or ise_ers_get_* tools which fetch specific ERS resources.

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 states when it performs a live probe (when nothing is missing AND probe is true) and that probe=true is the default. However, it doesn't explicitly state when NOT to use it or contrast with alternatives like ise_capabilities or ise_list_deployments. The deployment parameter guidance ('Omit for the only/default deployment') provides useful context, aligning with ise_set_default_deployment sibling semantics.

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