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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely new context: it is served by the authenticated current-user endpoint (auth requirement) and deliberately excludes account settings and credentials (scope boundary). It does not discuss failure modes when unauthenticated, but the annotations carry most of that weight.

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?

Two short sentences: the first front-loads the returned fields, the second adds endpoint and scope context. There is no repetition of the title and no filler.

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 zero-parameter read tool with no output schema, the description compensates by enumerating the exact fields returned and clarifying what is not included. Nothing an agent needs in order to call it correctly is missing.

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 schema has zero parameters, which is the baseline-4 case per the rubric. The description correctly adds no parameter guidance because none is needed, and instead spends its words on the returned field set.

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 verb and resource (show the connected user) and enumerates the exact fields returned (ID, company ID, name, email, default depot), so an agent knows precisely what it gets. It is unambiguously distinct from siblings like hirehop_get_job or hirehop_list_contacts, which operate on different resources.

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?

The 'connected / authenticated current-user' framing makes the use case clear (identify the caller), and 'excludes account settings and credentials' draws a useful scope boundary. It stops short of naming a sibling alternative or stating when-not to call it, so it lands just below the explicit when/alternatives bar.

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