agent_bootstrap

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

No annotations provided, so description carries full burden. It only mentions returning a default config but does not disclose any side effects, permissions, or whether it is a read/write operation. For a deprecated tool, minimal behavioral context is given.

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?

Exceptionally concise: one sentence plus deprecation notice. Every word serves a purpose, with the deprecation and replacement placed front and center.

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 it is deprecated and has no parameters, the description covers the basics. Output schema exists to explain return values. Slight lack: does not elaborate on use cases for unknown agents, but sufficient for a deprecated 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?

Tool has zero parameters, and schema coverage is 100%. The description correctly includes no parameter details because none exist. Baseline of 4 is appropriate as description adds no unnecessary information.

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?

Description clearly states the tool is deprecated and directs to 'agent_handshake' instead. It specifies the action ('Generic agent onboarding') and output ('Returns default config for unknown agents'), making the purpose unmistakable.

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 marked as deprecated with a direct replacement ('use agent_handshake instead'), providing clear when-to-use and when-not-to-use guidance. Also implies it is for unknown agents, but main guidance is the deprecation.

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