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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, yet the description reads as a pure informational lookup, and it adds no behavioral context of its own (permissions, whether a non-member can query, failure modes when the cell is unknown). Note the tension between the implied read-only query and readOnlyHint=false, though the fragment is too thin to be an outright contradiction. With annotations covering only the flag surface, the description should carry more of this burden and does not.

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?

It is short with no filler, but it is an under-specified sentence fragment rather than a concise specification. Brevity here costs information rather than saving it.

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 schema descriptions, so the description is the only place to explain what a successful result looks like (repo, owner list, team shape) and what happens on an unknown cell or unauthorized org. It supplies none of that for a two-parameter open-world 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?

Schema coverage is 0%: neither 'org' nor 'cell' is documented in the schema. The description only implicitly gestures at both ('a cell in the org') and gives no format, identifier style, or validation hints, so it does not compensate for the coverage gap.

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 fragment identifies the resource (a cell's ownership) and the fields returned (repo, owners, team), so an agent can guess it is an ownership lookup. But it is phrased as a noun clause rather than a verb+resource statement, and it never distinguishes itself from nearby siblings such as cells_find, my_cells, host_cell, or cell_call.

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?

There is no statement of when to call this versus alternatives, no prerequisites (does the caller need org membership?), and no exclusions. The agent must infer usage entirely from the name.

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