invoke_action

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It reveals that the request is a POST, that parameters become the JSON body, and how binding works. However, it does not mention potential side effects, required permissions, or return value behavior, which are important for a tool that invokes arbitrary actions that may mutate data.

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 four sentences, each earning its place: it names the operation, gives examples, explains boundness, and specifies parameter mechanics. The most critical information (invoke action, POST) is front-loaded, and there is no fluff or repetition of schema details.

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 no output schema and no annotations, the description covers the essential operation, bound/unbound distinction, examples, and parameter construction. It does not describe return values or error handling, but these are action-specific and would require knowing the individual action. The description is reasonably complete for the tool's complexity.

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 already provides 100% coverage with descriptions for all parameters, so baseline is 3. The description adds meaning by explaining the relationship: parameters become the JSON request body, entity_set+id are used for bound actions and neither for unbound. This clarifies the parameter usage beyond the schema's individual property descriptions.

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 the tool invokes a Dataverse Web API action via POST, with specific examples like PublishDuplicateRule and QualifyLead. It distinguishes from plain CRUD tools by saying 'Use for operations that are not plain CRUD', but does not explicitly name the sibling invoke_function, so the differentiation is implicit rather than explicit.

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 clear usage context: 'Use for operations that are not plain CRUD' and explains bound versus unbound actions with examples. It states when to pass entity_set+id versus neither, giving practical guidance. However, it does not explicitly name alternative tools (e.g., invoke_function for functions) or exclusions beyond the CRUD comment.

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