get_remote_assistance_ticket

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the bar is lower, and the description adds meaningful security-relevant context: the returned ticket grants a technician view AND control of the desktop session. That consequence is not derivable from the schema or annotations and is genuinely useful, though it omits any expiry/lifetime or scoping details for the ticket.

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, purpose front-loaded, second sentence supplying the behavioral consequence. No filler, no repetition of the tool name.

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?

With an output schema present, return-value documentation is not required, and the description nevertheless characterizes the return. Annotations cover the safety profile, so for a one-parameter tool this is largely complete; the only real omission is when-to-use guidance.

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 single parameter (session_id) is fully documented in the schema, so the description adds nothing about parameter meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Generate a Microsoft Remote Assistance ticket for a user session') and clarifies the artifact produced. It is distinguishable from session-management siblings like get_session or diagnose_session, though it doesn't explicitly contrast with them.

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 says what the tool produces but gives no guidance on when to reach for it versus the many sibling session tools (get_session, diagnose_session, etc.). No prerequisites, no exclusions, no named alternatives — usage is left entirely to inference.

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