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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true), so the bar is lower. The description adds a meaningful behavioral fact: 'Returns only data visible to the linked Market Brew account,' which discloses a scoping/authorization constraint not captured in annotations. However, it doesn't describe error behavior when the conversation isn't found or what the response contains.

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 use case. No unnecessary detail or repetition. Efficient, though the first sentence is effectively tautological.

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 tool with two undocumented required parameters, no output schema, and no explanation of return values, this description is far from complete. The scoping note is helpful but doesn't compensate for the missing parameter semantics and lack of output format guidance.

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% and the description mentions no parameters at all. With two required parameters (askWidgetId, conversationId) that are completely undocumented in both the schema and the description, the agent has no guidance on what these IDs are or how to obtain them. This is a critical 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?

States a clear verb ('get') and resource ('Ask conversation'), which tells an agent the basic purpose. However, it doesn't distinguish this from siblings like get_ask_chat_session or list_ask_conversations beyond the name, and the phrase 'Use this when the user asks to get an Ask conversation' is essentially a restatement of the tool name rather than an explanation of what data it retrieves.

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 offers no guidance on when to use this tool versus alternatives. There's no mention of when to prefer list_ask_conversations, get_ask_chat_session, or get_ask_widget. The only condition given ('when the user asks to get an Ask conversation') is tautological and doesn't help routing.

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