ponisha_list_conversations

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 the item shape (id, participants, unread_count, last_message, project/bid), but says nothing about authentication prerequisites, pagination behaviour, or total counts — gaps that matter for a live, open-world chat listing.

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?

Two short sentences, front-loaded with the action and scope, followed by the return shape. Nothing is repeated from the schema and no sentence is filler.

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 field enumeration is genuinely useful, and the tool is a simple parameterless read. However, for a paginated search-capable list it omits how 'q' behaves, what paging returns, and the auth requirement, leaving an agent to guess at iteration strategy.

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 33%: only 'q' is documented, while page and limit carry bounds/defaults but no descriptions. The description mentions no parameters at all, so it does nothing to compensate — it neither explains that 'q' is a free-text search over conversations nor that page/limit control paging.

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?

"List your chat conversations (with employers/freelancers)" gives a clear verb plus resource and names the actor scope (your own conversations), and the second sentence enumerates the returned fields. It does not explicitly distinguish itself from ponisha_get_messages or ponisha_get_conversation_info, so an agent must infer the listing-vs-fetching split.

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?

Usage is only implied: starting from 'your chat conversations' and returning ids suggests this is the entry point before calling ponisha_get_messages. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention that a session/login is required.

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