agent_handshake

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

No annotations are provided, so the description must disclose behavioral traits. It describes the tool as onboarding and returning config, but does not specify whether it is read-only, if it modifies state, or if it has side effects like registering the agent.

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?

Well-structured with a brief summary, a clear imperative to call first, and a bulleted list of arguments. Every sentence adds value without unnecessary verbosity.

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?

Covers the usage scenario well for an onboarding tool. The description does not detail the return value, but an output schema exists. Minor gap: it could hint at whether the configuration is saved or just returned.

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 input schema has 0% description coverage, but the description includes a detailed Args section with examples, units, and instructions for every parameter (e.g., '0 = auto-detect from model' for context_window). This fully compensates for the schema deficiency.

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 tool's purpose: 'Personalized agent onboarding' to 'Declare your environment and get optimal config'. It also explicitly says 'Call this FIRST when connecting to MidOS', distinguishing it from any other tool that might be called later.

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 explicit guidance to call this first and to pass as much info as possible. Although it doesn't explicitly mention when not to use or alternatives, the context makes it clear that this is the initial setup call.

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