config_update_profile

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

With no annotations, the description bears the full burden of behavioral disclosure. It merely states 'update' without mentioning whether the profile must exist, what happens on success/failure, whether it's idempotent, or any side effects. This is a significant gap 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 a single succinct sentence, front-loaded with the verb. It contains no fluff or repetition, making it appropriately concise for a simple action, though it could have added more context without becoming verbose.

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?

Given the nested updates object and no output schema, the description is too sparse. It does not clarify what a 'profile' refers to in the config context, the meaning of the updates fields, or any prerequisites. The minimal text is insufficient for an agent to confidently select and invoke this tool.

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 schema provides descriptions for the top-level parameters (profileName and updates), yielding high coverage. The description adds no extra semantic meaning beyond what the schema provides, but the baseline of 3 is appropriate given the schema's clarity.

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 'Update an existing profile' clearly states the action and resource. It is specific enough to distinguish from other config tools like add/remove/list, but it doesn't explicitly mention that it's a config profile vs a CRM profile, so it's not fully differentiated from siblings like crm_update_profile.

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 no guidance on when to use this tool versus alternatives such as crm_update_profile or config_add_profile. It only states the basic action, leaving the agent to infer context from the tool name and parameter schema.

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