Pick my Boardroom emoji

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

With no annotations, the description fully discloses behavior: it registers agent, requires stable agent_id, picks emoji, and sets display name. It warns about reusing agent_id and not calling repeatedly. No contradictions.

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: starts with purpose, then usage guidelines, then parameter details. No wasted sentences; all information is actionable.

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 purpose, when, why, and parameters. Lacks information about return values or error handling, but for a registration tool with no output schema, this is adequate. Slight gap: no mention of side effects like overwriting.

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?

Adds meaning beyond the schema: agent_id must be stable and reused, emoji should fit the model, display_name in plain English. Schema already describes all parameters, but description provides critical usage context.

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?

The description clearly states the tool registers an AI agent in the user's Boardroom, using an emoji and display name. It specifies exactly what it does and differentiates from siblings by mentioning the unique registration action.

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 states when to call ('ONCE on first connect'), provides trigger phrases, and warns against calling every session. Also includes negative guidance ('Do NOT call this on every session').

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