Read a LiveSwapFace page

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

With no annotations, the description carries the full burden and does disclose useful traits: read-only, freshness ("current"), no authentication, no media processing. It omits what happens for a non-allowlisted value, whether content is fetched live over the network, and whether output is plain text or structured.

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 with zero filler, and the resource scope is front-loaded before the safety caveat. Nothing is wasted, though there is also very little content.

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 one-parameter read tool with no output schema, the definition is broadly sufficient, but the return shape is only hinted at by "public text" and error behavior is unaddressed. A sentence on what comes back would close the gap.

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 single parameter has 0% schema description coverage, but the enum itself supplies the six valid page values. The description's phrase "allowlisted page" signals that the parameter must be one of a fixed set, adding some meaning, yet it does not explain the enum entries or what each page contains.

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?

"Read current public text from one allowlisted LiveSwapFace page" gives a specific verb (read) and resource (a page's public text), plus a scope constraint (one allowlisted page). It is distinguishable from get_official_links and estimate_session_credits, though it never names those siblings to sharpen the contrast.

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 exclusions ("No account access or media processing") implicitly frame when this tool applies versus account-scoped alternatives, but there is no explicit when-to-use statement or reference to the sibling tools. The agent must infer the routing itself.

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