Mesh Bootstrap

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the description still needs to explain what actually mutates. It does not: nothing indicates that setting 'key_pfx' creates new keypairs (rotate_key), that 'cfg'/'rmt_cfg' rewrite remote SSH config, or that 'preview' is the only safe dry-run. The schema carries this information, not the description.

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 with no filler and no buried content, so it is efficient in form. But 'appropriately sized' is not met: a 16-parameter, six-mode dispatch tool compressed to one sentence of noun phrase leaves the reader less informed than the name plus schema alone.

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 values need not be explained, but the description still omits the operation-selection logic, the fan-out scope, and the fact that multiple behaviors live behind one entry point. For a zero-required-parameter tool where the caller must set the right combination to get a given operation, that is a material gap.

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 documents all 16 parameters, including host precedence, preview semantics, and resolved_hosts. The description adds no parameter meaning at all – not even which parameter selects which operation – so it sits at the baseline for fully documented schemas.

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 says 'Bulk inventory operations against YAML host groups', which is a vague restatement of the name rather than a specific verb+resource. The tool actually dispatches six distinct operations (run_command, send_file, receive_file, copy_ssh_config, rotate_key, configure_key_auth), but none of them are named, so an agent cannot tell what this does apart from tm_inventory_run_command or tm_inventory_send_file.

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?

No when-to-use, when-not-to-use, or alternative is mentioned, even though the sibling list contains single-operation counterparts for every capability this tool bundles. The only implicit hint is the word 'bulk', which hints at fan-out scope but does not give the agent any rule for choosing this tool over a sibling.

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