remote_profile_create

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

No annotations are provided, leaving the description to carry the full behavioral burden. The description only states 'Create a saved profile' and suggests using environment references, but it does not disclose whether the tool overwrites existing profiles, rejects duplicates, or requires specific permissions. This is insufficient for a mutation 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?

The description is two short sentences, with the primary action front-loaded. The second sentence is substantive and not redundant. There is no wasted 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?

Despite having an output schema, the tool's complexity (a free-form settings object) requires more guidance on how to construct valid input. The description lacks information about required settings fields, validation behavior, and interaction with existing profiles, making it incomplete for reliable 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 input schema provides only parameter names ('name', 'settings') with zero description coverage. The description adds value by mentioning 'password_env' and 'passphrase environment references', giving a clue about the contents of the 'settings' object. However, it does not explain the full structure or provide examples, leaving significant ambiguity.

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 the verb 'Create' and clearly identifies the resource as 'a saved profile', distinguishing it from sibling tools like remote_profile_update and remote_profile_delete. The second sentence about password_env is a supplementary note, not the core purpose, which remains 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?

The description provides a usage hint ('Prefer password_env and passphrase environment references') for constructing the settings object, but it does not explicitly state when to use this tool versus remote_profile_update or remote_profile_rename. There is no mention of alternatives or prerequisites, so it only implicitly conveys that this is for creating new profiles.

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