ateam_bootstrap

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

With no annotations, the description carries the full burden. It discloses that the tool returns platform explanation, example solutions, and assistant behavior instructions, and mandates its use. It does not explicitly state whether any side effects occur (e.g., marking onboarding as complete), but the read-only nature is implied by 'Returns.' Given the absence of annotations, this is clear but could be more explicit about side effects or state changes.

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?

The description is concise, front-loaded with 'REQUIRED,' and every sentence serves a purpose: identifying the entrypoint, listing trigger conditions, and specifying return content. It ends with a direct behavioral instruction. No waste.

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?

Given the tool's simplicity (no parameters, no output schema), the description is complete. It covers what the tool does, when to use it, and what it returns. The extensive sibling list doesn't necessitate additional context because the tool's role as the universal onboarding entry point is unambiguous.

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 tool has zero parameters, so the baseline is 4. The description need not explain parameter semantics, and it doesn't attempt to. The schema already covers all parameters (none), and the description adds no unnecessary detail.

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 identifies the tool as the 'REQUIRED onboarding entrypoint' and states its function: returns platform explanation, example solutions, and assistant behavior instructions. It distinguishes itself from siblings by being the introductory entry point, with a specific verb ('bootstrap') and resource ('A-Team MCP').

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?

Usage conditions are explicitly listed: must be called on greetings, help requests, capability exploration, or first connection. The instruction 'Do NOT improvise an introduction — call this tool instead' provides a clear exclusion and directs to the tool over improvisation. This exceeds simple context by naming both when and when not to use alternatives.

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