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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses the material consequences: the agent can run rigs, read saved keys/OAuth grants, and spend budget. That is exactly the risk context an agent needs before invoking a non-read-only tool.

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?

Three sentences, front-loaded with the core action before the auth-behavior caveats. Dense and largely waste-free, though the closing sentence ("This is the door to...") is promotional rather than informational.

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?

Output schema exists so return values need not be described, and the critical auth/permission model is covered. What remains unaddressed is failure behavior (e.g., unknown agent name) and latency/streaming characteristics of a conversational tool.

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%, so the baseline is 3; the description adds the default agent identity ('rokha-agent'), which the schema only shows as an example. There is a mild tension with the schema marking agent_name as required while the description implies a default, which keeps it from a 5.

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?

"Send a message to a Rokha agent ... and get its reply" gives a specific verb, resource, and round-trip outcome, plus the default agent name. It is clearly distinguishable from the surrounding registry/rig/auth tools, which do not involve agent conversation.

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?

It states the two usage regimes explicitly: authenticated callers get an agent acting as them, anonymous callers get general chat only. That is clear when-to-use context, though it does not name an alternative tool or say when not to use this entry point.

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