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

With no annotations, the description carries the full burden and succeeds. It discloses that names and profiles are unverified, instructs the agent to compare verification phrases through existing conversation, and warns against approving based on the request alone. This is critical anti-spoofing behavior not inferable from the schema.

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 short, front-loaded with the tool's action and scope, and each sentence adds essential information. The safety caveats are compact and high-value.

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?

For a simple tool with one optional parameter and no output schema, the description covers the core behavior and provides important safety context. It does not describe the return format or pagination, but the main use case is adequately specified.

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 single optional 'connection' parameter is already fully documented in the input schema with 100% coverage. The description adds no parameter-specific meaning, but none is needed because the schema handles it.

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 opens with 'Creator only: review pending join requests and recent decisions across the account', stating a specific verb, resource, and scope. This clearly distinguishes it from action-oriented siblings like join_request_decide.

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 gives clear context by restricting usage to the creator and framing the tool as a review step. It does not explicitly name sibling alternatives or state when not to use it, but the intended role in the join-request workflow is evident.

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