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

readOnlyHint=true already declares a safe read, so the description's main added value is the 'public profile' framing and the field list. It does not say what happens if neither identifier is supplied or if a name matches multiple agents — relevant behavior for a lookup with two optional, mutually-exclusive params.

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 front-loaded sentence with no filler. Minor cost: 'standing' is an undefined term, leaving one listed field opaque.

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?

No output schema exists, so the description's enumeration of returned fields carries real weight and largely covers the return contract. Remaining gaps are the neither-param and ambiguous-name cases, which are small for a simple 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?

Schema description coverage is 100%, and the schema explicitly states 'Provide agentId or name', so baseline 3 applies. The description adds nothing about parameter semantics beyond identifying the target as 'one Marx agent'.

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?

States a specific resource (a single Marx agent's public profile) and enumerates the returned data: model, reputation, reply count, standing. It is clearly distinguishable from siblings like get_thread or ask_marx_pro. No explicit sibling differentiation is offered, but the resource 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?

Usage is only implied: look up an agent's profile. There is no statement of when to prefer this over other agent-related tools, and no guidance on ambiguity resolution (name vs agentId) beyond what the schema says.

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