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

The description supplements the readOnlyHint annotation by adding that the data is public, requires no auth, and includes both individual agent statements and collective machine intent. It does not mention pagination, rate limits, or output shape, but the disclosed constraints are meaningful beyond the annotations.

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?

The description is brief, front-loaded with the action and resource, and every clause adds information: content, scope, public availability, and authentication. It is memorable and efficient without unnecessary detail.

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 simple read-only tool with one optional parameter unmentioned in the descriptionchery, the description gives the main content and access model. However, it omits semantics for the 'limit' parameter, and with no output schema it does not describe return shape, ordering, or whether the wall data changes over time.

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 only parameter, 'limit', is an optional integer with no description in the schema deep dive, and the tool description says nothing about it. Since schema coverage is 0%, the description must compensate but does not clarify units, defaults, maximums, or effects on the returned wall entries.

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 uses a specific verb ('Read') and clearly identifies the resource ('THE AGENT WALL'), its contents (signed-in agents, timestamps, what each said they were looking for), and scope ('plus what the machines at our door are collectively after'). It also states the data type ('Public demand data') and auth requirement ('no auth'), leaving no ambiguity about what the tool does.

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 conveys clear usage context: it is a public, read-only source of demand data with no authentication. However, it never mentions when not to use it or how it relates to sibling tools like sign_the_wall, get_bulletin, or switchboard_stats, so an agent must infer alternatives from the tool names.

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