d365fo_delete_profile

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

With no annotations provided, the description effectively discloses the key behavioral trait: 'Automatically invalidates all cached client connections since the profile is no longer available.' This adds important context beyond the simple delete action.

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 very concise, using only three sentences plus an Args/Returns section. It is front-loaded with the main purpose and uses clear structure, making it easy for an AI 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 simple delete tool with one required parameter, the description covers the core behavior, side effect, and return value. It is complete enough given the tool's simplicity, though it could mention prerequisites like profile existence.

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 specifying that profileName is the 'Name of the profile to delete,' which provides clear semantics beyond the schema's minimal 'Profilename' label. Given 0% schema description coverage, the description compensates well.

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 'Delete a D365FO environment profile,' which is a specific verb and resource. This clearly distinguishes it from sibling tools like create_profile, update_profile, or search_profiles.

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 mentions the side effect of invalidating cached connections, which gives context for using the tool, but it does not explicitly state when to use this tool versus alternatives or when not to use it. No comparison to other profile-related tools is provided.

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