d365fo_set_default_profile

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

With no annotations, the description takes on the full burden. It discloses a key behavioral trait: 'Automatically refreshes all cached client connections since changing the default profile may affect client resolution.' This is valuable, though it could also mention potential permission requirements or irreversibility.

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 (~70 words) and well-structured: a clear header line, a paragraph explaining the side effect, and structured Args/Returns sections. Every sentence adds value.

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 tool's simplicity (one parameter, no enums, output schema exists), the description is mostly complete. It explains the main function and side effect. However, it could mention error cases (e.g., profile not found) or confirm the result behavior.

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 has 0% description coverage, so the description must compensate. The Args section provides a basic description: 'Name of the profile to set as default.' This adds some meaning beyond the schema, but it lacks details like validation rules or expected format.

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 clearly states 'Set the default D365FO environment profile,' which is a specific verb+resource. It distinguishes itself from sibling tools like d365fo_get_default_profile and d365fo_create_profile by indicating a set operation.

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 does not provide guidance on when to use this tool versus alternatives. It mentions a side effect but lacks explicit context like 'Use this to change the active profile' or 'Do not use if you only need to create a new profile.'

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