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

With no annotations, the description carries the full behavioral burden. It usefully discloses the filtering rule ('only members who accepted their invitation appear') and the read-only nature is implied. It omits pagination, permissions, and ordering behavior, leaving real gaps for an unannotated tool, though the output schema covers return 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?

Very short and front-loaded: the resource is stated first, then the id semantics that matter for callers. The line breaks are a bit arbitrary but no sentence is wasted.

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 read-only lookup with an output schema, the description covers purpose, the key output field's semantics, and the visibility rule. Missing only minor operational details like pagination or ordering, which are low-risk here.

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?

All five parameters are generic oto context fields (_org, _group, _run_id, _project, _instance) fully documented at 100% schema coverage, so the schema already does the heavy lifting. The description adds no meaning about any parameter; it only explains how the tool's output id is consumed elsewhere.

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 names a specific resource and scope: 'Active team members of the Minari company,' which clearly distinguishes it from siblings like minari_contact or minari_call. It does not use an explicit verb (list/get), but the noun phrase is unambiguous about what is returned.

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 concrete downstream usage: the returned `id` is what every `user_id` filter expects and what `minari_list(op="create")` needs as `assigned_to`. This steers the agent toward calling it before filtered lists or creates. It stops short of stating exclusions (e.g., when to use minari_contact instead).

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