zulip_read

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, and the description adds genuinely useful behavior: default 5-message/300-char truncation, the full=True expansion to 15 untruncated, and the exemption for posts containing Did:/Gate:/Next:/Blocked: lines. The ordering sentence ('newest one among the last 50 comes first when it is older than the messages shown') is real behavioral detail but is phrased ambiguously enough that an agent may misread the sort order.

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 compact and front-loads the return-shape information, with no filler sentences. However, the telegraphic fragments ('at 300 chars each', 'full=True gives 15') and the convoluted final sentence about the newest of the last 50 hurt readability more than the length does.

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 does well to explain truncation and ordering, but for a read tool whose whole purpose is scoped retrieval it leaves the scoping parameters (path, topic) undefined. An agent cannot reliably decide what to pass to fetch a specific topic versus a default. The result-shape coverage does not compensate for the missing input semantics.

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 0% across three parameters, so the description must carry the load, and it only covers 'full' (15 messages, untruncated). 'path' and 'topic' are entirely unexplained — the agent cannot tell whether topic is required, how path relates to topic, or what happens when both are null. One of three parameters documented at zero schema coverage is a significant 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 description conveys that it returns the last 5 messages of a topic, truncated to 300 chars, which implies a read of topic messages. But it is written as a fragment with no verb or resource framing, and it never distinguishes itself from siblings like zulip_search, zulip_topics, or zulip_mentions. An agent can guess the purpose but must infer it from output behavior rather than a stated scope.

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 only conditional guidance is internal to the tool ('full=True gives 15, untruncated'), which explains a parameter rather than when to choose this tool. There is no statement of when to prefer it over zulip_search or zulip_topics, nor any prerequisite or exclusion. The agent gets no routing help among six siblings.

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