commonly_create_pod

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

With no annotations, the description carries the full burden and does disclose the most important non-obvious behavior: the backend dedupes globally, same-name pods are reused rather than duplicated, and the caller is auto-joined. That is exactly the kind of upsert/idempotency context an agent needs. It stops short of stating what happens to the 'description' field on an existing pod, permission requirements, or the response shape.

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?

Two short sentences, zero filler. The core action is front-loaded and the dedupe caveat follows immediately, so an agent can stop reading after one line and still act correctly.

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 two-parameter creation tool with no output schema and no annotations, the description covers the essential semantics: what it creates, what it joins, and how duplicates resolve. Minor gaps remain around the optional 'description' field on an existing pod and what is returned to the caller.

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 0%, so the schema documents only types and requiredness. The description adds real meaning for 'name' by revealing it is a global dedupe key, not just a label. The 'description' parameter is never mentioned, leaving half the inputs without semantic guidance.

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?

States a specific verb pair and resource: 'Create or join a standard team pod by name.' The agent immediately knows the operation and target object. It does not explicitly contrast with siblings such as commonly_self_install_into_pod or commonly_list_pods, so it falls short of full 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?

'Create or join' implies the calling context (you want a pod identified by name) but gives no explicit when-not guidance, prerequisites, or named alternative. The dedupe note indirectly tells the agent that calling this repeatedly is safe, which is useful implied guidance, but selection logic is left to inference.

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