lookup_errorExact/substring match against all known Copilot Studio error codes and error messages in the register. The fastest path when you have a verbatim error string (e.g. "FlowActionTimedOut"). Returns the matching record(s) with the citable URL.
| Name | Required | Description | Default |
|---|---|---|---|
| error | Yes | The error code or error message, as verbatim as possible. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description complements annotations (readOnlyHint, openWorldHint) by stating it returns matching records with a citable URL, adding value beyond the structured fields.
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?
Two sentences efficiently convey purpose, usage, and output without any wasted words or redundancy.
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 single-parameter lookup tool with no output schema, the description fully covers what the tool does and what it returns, and annotations handle safety concerns.
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?
Schema coverage is 100% and the description largely reiterates the schema's parameter description ('as verbatim as possible'), adding minimal new semantic meaning.
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?
Clearly states it performs exact/substring matching against known Copilot Studio error codes and messages, distinct from sibling tools which deal with drift, friction, and patterns.
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?
Explicitly indicates it is the fastest path when you have a verbatim error string, implying when to use; does not explicitly mention alternatives but context makes the use case clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: overview, specific record, pattern retrieval, listing, error lookup, and search. No overlap in functionality.
All tool names follow a consistent 'verb_noun' pattern (e.g., get_current_drift, list_frictions, lookup_error), with clear action and object.
Seven tools cover the domain comprehensively without being excessive. Each tool serves a specific need for querying the friction index.
The tool set provides complete read access to the friction index: overview, detailed records, patterns, listings with filters, error lookup, and full-text search. No obvious gaps for a read-only register.