detach_reference_from_agent

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

Discloses important behavior: the response is the server's answer, not a success claim; detach on non-existent link reports that instead of failing. No annotations provided, so description carries the full burden and does well.

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?

Concise, front-loaded with the main action, includes necessary caveats. A minor suggestion: could be slightly tighter but overall well-structured.

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?

Adequate for a simple two-parameter tool, but lacks details about the response structure. The suggestion to use list_agent_reference_docs helps verify outcome, but more completeness on expected return values would improve.

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 description coverage is 0% and the description does not elaborate on the parameters. AgentId and refId are inferred from the tool name, but no additional details about format or constraints are given.

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 the action 'Unscope a reference from an agent' and explains it only removes the link, not the reference. Distinguishes from potentially similar operations like deleting reference docs.

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?

Provides context for when to use (to remove a link) and suggests confirming with list_agent_reference_docs. Does not explicitly state when not to use but implied by the description.

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