embrace_list_readonly_tools

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

With no annotations, the description is the sole source of behavioral information. It correctly implies a read operation and states the return format (full JSON), but it does not disclose any other behaviors such as potential size limits, whether all read-only tools are included, or if there are any side effects. For a simple listing tool, this is adequate but minimal.

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?

A single sentence that is front-loaded and carries no fluff. Every word contributes to the tool's purpose.

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?

The tool has an output schema and zero parameters, so the description covers the essential purpose. It might mention that it is the authoritative source for schemas, but given the low complexity and presence of the output schema, the description is nearly complete.

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 tool has zero parameters, so the description needs no per-parameter explanation. Baseline for zero parameters is 4, and the description adds no irrelevant information about parameters.

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 states a clear verb ('Return') and specific resource ('official Embrace read-only tool schemas as full JSON'), making it obvious what the tool does. It is distinct from the sibling embrace_call_readonly, which presumably calls a specific tool rather than listing schemas.

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 gives no guidance on when to use this tool versus embrace_call_readonly or any other alternative. It does not explain typical use cases or prerequisites, leaving the agent to infer when listing schemas is appropriate.

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