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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: deployment_commit is null unless the host supplies it, skill_version_recommended is uncached/never auto-updates, and output matches GET /api/official. Caching and side-effect-free behavior are disclosed 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?

Front-loaded with the operation, followed by precise clarifications of two specific fields and a routing pointer. The opening sentence is a heavy seven-item noun pile, but each following sentence earns its place by disambiguating a term.

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 and no parameters, the description carries the burden of explaining the return payload and does so by naming each fact and clarifying the two ambiguous ones (deployment_commit, skill_version_recommended). It could be more complete on overall response shape, but it is sufficient for a host-integration read tool.

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?

There are zero parameters, so the baseline is 4. The description correctly implies a parameter-free read and spends its detail on returned fields rather than nonexistent inputs.

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 ('Read') and resource ('canonical domain, treasury, Base USDC, no-token statement...') and enumerates the concrete facts returned, which lets an agent distinguish it from siblings like list_world or home. The enumeration is dense jargon, but the purpose is unambiguous.

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?

It notes the response equals GET /api/official and adds a routing hint ('Lost? Call front_door'), which implies usage. However, it never states when to prefer this over alternatives such as home, list_world, or search, so guidance is only implied.

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