remote_profile_create

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

Annotations already cover the safety profile (not read-only, idempotent, non-destructive, closed-world), so the description only needs to add context. It does add one useful piece: credentials should be supplied as environment references rather than inline secrets. It says nothing about what happens when a profile with the same name already exists, despite the idempotent hint.

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 short sentences with no filler, and the security guidance is front-loaded. However, the brevity is under-specification rather than efficiency, since the settings object needs explanation.

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 are covered. But a mutation tool that persists a secret-bearing profile, with an unconstrained settings object and no mention of failure modes or duplicate-name behavior, leaves the agent guessing on the parts that matter.

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 0% and the two parameters are named only. The critical parameter is a free-form nested settings object with additionalProperties, so the description is the only place that could enumerate valid keys, yet it names just two of them (password_env, passphrase) without format or placement. Most of the parameter surface remains opaque.

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?

"Create a saved profile" states a specific verb and resource, and the remote_profile_* sibling set makes the target clear. It doesn't explicitly contrast with remote_profile_update or remote_profile_get, but the create semantics are unambiguous.

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?

"Prefer password_env and passphrase environment references" is a parameter preference, not when-to-use guidance. Nothing tells the agent when to create a profile versus updating an existing one, or what prerequisites (e.g., inventory initialized) apply.

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