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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real context beyond that: the call is scoped to the caller's own identity (auth implied) and returns a subset of data that also appears in problee_get_me, which warns the agent about overlap and potential redundancy.

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, each carrying information: the first defines the content, the second defines the relationship to the sibling and the reason to exist. Nothing is redundant with the title.

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?

With an output schema present, rich annotations, and no inputs, the description covers everything an agent needs: what it returns, whose data it returns, and how it relates to problee_get_me.

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 the baseline is 4; there is nothing for the description to disambiguate and it correctly says nothing about inputs.

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 ('own reputation tiers and available capability gates') and scopes it to the authenticated agent, which cleanly separates it from sibling reputation tools such as problee_get_agent_reputation, problee_get_counterparty_reputation and problee_get_subject_reputation.

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?

Explicitly frames the tool as a standalone extraction of the `reputation` slice from problee_get_me, telling the caller when to pick this instead ('callers that only need this'). It stops short of an explicit inverse rule ('use problee_get_me when you also need balance/identity'), so it is clear but not fully bidirectional.

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