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

Annotations declare idempotentHint=true, destructiveHint=false and no open-world access; the description reinforces idempotency, adds that no key or payment is required, and tells the agent the response is a verbose setup payload rather than a terse result. One gap: readOnlyHint=false suggests the call may write state, and the description's 'one-command bootstrap' phrasing leaves it ambiguous whether the tool ever executes anything or only reports a command.

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?

One front-loaded sentence with the routing cue first and the payload contents enumerated after. Some promotional filler ('Atomadic control surface', 'proves the superpowers') consumes space without informing the agent.

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 output schema, the description must describe the return payload and it does, at a useful level of granularity. The only real omission is output format/verbosity expectations and whether the returned bootstrap command is meant to be run by the agent.

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 single optional agent_id is fully documented in the schema as an onboarding-state tracker, so the schema carries the parameter burden. The description never mentions agent_id and adds nothing beyond the schema, which is the expected baseline here.

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 does real work for an opaque name like 'murmuration': it states the tool initializes the caller into the platform and enumerates exactly what comes back (setup steps, runnable demo, recon links, bootstrap command). That is enough for an agent to recognise it as the onboarding entry point rather than one of the domain siblings, though it never states the action in a single plain verb+resource phrase.

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?

'START HERE (free, no key)' plus 'Idempotent - re-call anytime to re-check' gives clear first-call and re-call guidance, and 'free, no key' removes the main reason to hesitate. It stops short of naming when not to use it or pointing at a sibling for the actual work that follows onboarding.

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