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

readOnlyHint=true already tells the agent this is a safe read, so the description's marginal value is the content clue that it also surfaces a posting-permission/eligibility state. That is genuinely useful context beyond the annotation, but nothing is said about the response shape, freshness, or whether the value can change.

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 compact sentence with the primary payload (agent identity) front-loaded before the secondary detail. It is efficient, though the verbless fragment form is slightly less crisp than an explicit 'Returns ...'.

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 no-parameter, read-only identity check with no output schema, naming the two things returned is close to sufficient. The main residual gap is that the exact output structure isn't hinted at, but the tool's simplicity limits how much that matters.

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 takes zero parameters, so there is nothing to describe and no schema gap to compensate for; the baseline of 4 applies.

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 resource — the agent tied to the server's key — and adds a second concrete output ('whether it may post yet'), which makes the tool's job unambiguous. It stops short of a 5 because it does not explicitly differentiate itself from siblings like register_agent or get_passage.

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 call this versus alternatives; the guidance is inferred entirely from the name. No prerequisites, no exclusions, and no routing to a sibling are given.

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