endpoint_assign_profile

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

With no annotations, the description fully discloses the write nature, high risk, reversibility, and the fact that prior profile is captured for undo and audit trail. This provides substantial behavioral context beyond the basic action, though it could still mention potential side effects or failure modes.

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 concise and well-structured: a one-line summary then a clear Args block. Every sentence provides value without verbosity, making it easy for an agent to parse quickly.

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?

For a tool with 3 parameters and no output schema, the description adequately covers the action, impact (reversible, audit trail), and parameter usage. It does not mention success responses or error states, but the description is sufficient for a typical assignment operation.

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 description includes an Args section explaining each parameter: endpoint_id as 'as returned by endpoint_list', profile_id as 'Config profile to assign', and target as 'Endpoint-management target name from config; omit for the default.' Since the schema has 0% description coverage, this adds crucial meaning that aids agent invocation, though some explanations are minimal.

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 starts with 'Assign a config profile to an endpoint (reversible)', which clearly states the action and resource. The additional detail about capturing prior profile and providing undo further clarifies the tool's specific function, distinguishing it from sibling tools like endpoint_get or endpoint_list.

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 explicit guidance on when to use this tool versus alternatives. While it mentions the undo and audit trail, it does not specify contexts where assignment is appropriate or when to prefer other tools. The absence of usage scenarios or prerequisites limits the agent's decision-making.

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