MCP Dynamics CRM Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Remove' implies a destructive mutation, the description doesn't specify whether this operation is reversible, what permissions are required, whether it triggers side effects, or what happens to associated data. For a deletion tool with zero annotation coverage, this is insufficient behavioral context.

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, efficient sentence in Portuguese that gets straight to the point. There's no wasted verbiage or unnecessary elaboration. However, it could be slightly more structured by explicitly stating it's a deletion operation for Dynamics plugin steps.

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 destructive deletion tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after deletion, whether there are confirmation prompts, error conditions, or what the tool returns. The description should provide more context about this potentially irreversible 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 schema description coverage is 100% with the single parameter 'stepId' fully documented in the schema. The description doesn't add any parameter information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 'Remove um step de plugin registrado' clearly states the action (remove) and target (registered plugin step) in Portuguese. It's specific enough to understand the tool's function, though it doesn't explicitly differentiate from sibling tools like 'dynamics_remove_solution_component' or 'dynamics_delete_solution' which might have overlapping deletion purposes.

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. There are several sibling deletion tools (dynamics_delete_column, dynamics_delete_solution, dynamics_delete_web_resource, dynamics_remove_solution_component) with no indication of when this specific plugin step deletion is appropriate versus other deletion operations.

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