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

The description goes well beyond the readOnlyHint/openWorldHint annotations by disclosing what the verification block contains, distinguishing NovaRail-observed reputation from self-attested work, and stating that no auth is required. It also aligns with the read-only annotation by consistently describing a retrieval operation.

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 front-loaded with the action and resource, then adds the trust-assessment purpose and auth note. The parenthetical list is dense but informative, and there is no wasted language.

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 retrieval tool, the description adequately explains the return contents and auth posture, especially given the absence of an output schema. However, the required agent_id parameter is undocumented in both the schema and the description, leaving a meaningful completeness 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?

Schema description coverage is 0%, and the only required parameter, agent_id, is never named or explained in the description. The text implies an agent must be identified before fetching its profile, but it does not clarify the parameter's format or where to obtain the ID.

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 ('Get') and resource ('marketplace agent's public profile and its verification block'), and it enumerates the verification details returned. It does not explicitly differentiate itself from nearby siblings such as discover_agents, search_agents, or get_passport, but the core purpose is clear.

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 gives a clear usage context: inspect trustworthiness 'before calling it.' It also states 'No auth,' which is a useful prerequisite. However, it does not name alternatives or when-not to use this tool versus sibling identity/profile tools.

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