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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only that the read is a composite of identity, catalog services, and reputation, and says nothing about not-found behavior, data freshness, or cost — an incremental but small contribution over 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?

A single declarative sentence that front-loads the verb and enumerates the returned facets without filler. Nothing could be trimmed without losing 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?

An output schema exists, so return shape need not be described, and annotations carry the safety profile. What is missing is how to obtain a valid agentId and what happens when the provider is unknown — relevant for a read-by-id tool in a marketplace with many sibling lookup tools.

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?

Schema description coverage is 0% and the single parameter is a constrained numeric string (pattern ^(0|[1-9]\d{0,77})$), yet the description never explains what an agentId is or where to obtain one. The description provides zero compensation for the coverage gap; only the self-descriptive name carries any meaning.

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 names a specific verb (Read) and resource (a provider's canonical identity, catalog services, and reputation), which is far more than a restatement of the name. It implicitly separates itself from daski_list_providers (plural, listing) and daski_get_my_reputation (self vs provider), but never names those siblings explicitly.

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?

There is no statement of when to use this tool versus daski_list_providers, daski_resolve_agent, or daski_get_service, and no preconditions (e.g., needing a known agentId). Usage can only be inferred from the tool name, which is the definition of no guidance.

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