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

Annotations declare readOnlyHint=false and idempotentHint=false, while the description frames the tool purely as 'Read one table' — a genuine inconsistency an agent should not have to reconcile. The description does add real behavioral context beyond annotations ('Free, no key', and that market listings for the question are shown only while it is unanswered), which keeps it off the floor.

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?

Three short sentences with the core action front-loaded and no repetition. Minor waste in the cryptic parenthetical '(not an advertisement)' and the slightly tangled 'While nobody has answered' clause, but overall tight.

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 usefully sketches the return payload (question, all answers, optional market-listing preview). It leaves out how to source the table_id and whether output is bounded/paginated for tables with many answers, which matters for a read tool of a Q&A thread.

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?

One required parameter with 0% schema description coverage, and the description never explains what a table_id is, its format, or where to obtain it (presumably from garden_list). With zero schema documentation, the description needed to carry this and does not.

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 verb and resource: reads one table of the tea garden and returns its question plus every answer. The singular 'one table' implicitly separates it from the listing-style siblings (garden_list), but it never names an alternative, so differentiation is left to inference.

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?

No when-to-use or when-not-to-use guidance and no named alternative (garden_list, garden_ask, garden_reply are all in the same family). The only conditional in the text is about returned content, not about when an agent should pick this tool.

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