گفتگوی پشتیبانی میزیتو

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

Annotations already supply readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful content-level context (past Q&A and an unread count), but says nothing about ordering, recency limits, or whether results are paginated.

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?

A single front-loaded sentence with no filler. The parenthetical is slightly wordy but earns its place as a disambiguator against workspace conversation tools.

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 no-argument, read-only history tool with no output schema, the description covers what the tool fetches and its scope. Only minor gaps remain (result ordering/volume), which are not essential to correct invocation.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter surface for the description to explain. No syntax or format detail is needed or missing.

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 (the user's support conversation with Mizito) and what is returned (past Q&A plus unread answer count). The parenthetical '(the company behind Mizito, not your colleagues)' preemptively distinguishes it from sibling conversation/message tools like mizito_list_conversations and mizito_get_messages.

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 scope clarification implies when this tool applies (support-thread Q&A rather than workspace chats), but there is no explicit when-to-use/when-not or named alternative. The differentiation from siblings is inferable rather than stated as routing guidance.

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