Load Specialist Context (alias)

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the useful behavioral note that it does not hire people, and clarifies the alias relationship with workforce_as, going beyond what annotations provide without contradicting them.

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 extremely concise—two short sentences—and every element earns its place: the alias reference, the purpose, and the hiring disclaimer. Zero wasted words.

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?

The rich schema and annotations cover safety and parameter semantics. The alias to workforce_as provides a reference point for further details, and the hiring disclaimer addresses a likely misuse. Still, the description does not elaborate on what 'specialist context' entails or when to prefer this over other sibling tools, so a small gap remains.

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 description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional parameter-specific meaning, but it does not need to since the schema is complete. Baseline 3 is appropriate.

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 loads specialist context for the agent to perform specialized work. It uses a specific verb ('load') and resource ('specialist context'), and explicitly distinguishes itself from being a hiring tool, which aligns with sibling differentiation.

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?

The description identifies this as an alias of workforce_as, which tells the agent it behaves identically to that sibling, providing clear usage context. It also notes 'Not a hiring tool' as an exclusion, but does not explicitly name alternatives or when-not-to-use scenarios beyond that.

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