اعضا و تنظیمات یک گفتگو

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful payload context (what fields come back, including mute state and open tasks), but says nothing about access constraints, visibility scope, or behavior when the conversation is inaccessible.

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?

One front-loaded sentence that leads with the resource and then lists the returned facets, with no filler. The parenthetical type enumeration is dense but earns its place by pre-answering what values to expect.

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?

With no output schema, the description must describe the return shape, and it does so concretely (title, type, members with admins, mute state, linked project, open tasks). For a one-parameter read-only tool this is close to sufficient, though it omits any note on visibility limits or how much member/task data is returned.

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 100% and the single parameter is fully documented, including its provenance from mizito_list_conversations and mizito_get_project. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 resource and enumerates the returned facets: title, type (with the enum of conversation kinds), members/admins, mute state, linked project, and open tasks. It clearly reads as a single-object fetch rather than the list sibling, though it never names mizito_list_conversations explicitly.

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?

The description gives no when-to-use, when-not-to-use, or alternative-tool guidance. The only routing hint ('conversation_id comes from mizito_list_conversations / mizito_get_project') lives in the schema, not the description, so the prose itself carries no usage context.

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