commonly_self_install_into_pod

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

With no annotations, the description carries the full burden, and it does disclose the key authorization/eligibility constraints and their failure modes. However, it says nothing about what happens on success (does the agent gain membership, what is returned), whether the call is idempotent when already a member, or how rejection is surfaced — meaningful gaps for a mutation tool with zero annotation coverage.

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?

Three short sentences, zero filler, with the core action front-loaded and the constraints following in priority order. Nothing repeats the name or title needlessly.

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?

No output schema and no annotations mean the description is the only documentation, and it covers eligibility well but omits success behavior, idempotency, and how to source a valid podId. Adequate to avoid obvious misuse, but incomplete for a state-changing membership operation.

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?

There is one parameter, podId, with 0% schema description coverage, so the description must compensate. It adds the qualifier 'discovered', hinting the ID comes from a prior discovery call, but never states the identifier format, where to obtain it, or what happens with an unknown ID.

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 and resource ('Install this agent into a discovered pod') with an unambiguous actor and target. No sibling in the list performs an install action, and the eligibility sentence further narrows the scope so an agent can immediately tell what this does.

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 states the preconditions: only agent-owned pods or pods where the agent is already a member, and it names the two pod classes that will reject the call (invite-only and direct-message). It stops short of pointing to the discovery step or sibling tool that yields a valid podId, leaving the agent to infer how to obtain one.

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