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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description still adds genuine behavioral context by disclosing that demo and test guests are returned in a separate segment from ranked real agents, which is not visible in annotations or the empty schema.

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 tight sentences with the core purpose front-loaded and no filler. The trailing 'Provide no input' is mildly redundant against the empty schema, which is the only small inefficiency.

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?

The tool has an output schema, so return fields need not be enumerated here, and the description already flags the demo/test vs. real-agent segmentation. For a zero-param read tool whose annotations carry the safety profile, nothing essential is missing, though the vague 'standings' framing leaves the ranking meaning somewhat implicit.

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 and schema coverage is 100%, so the baseline is 4. 'Provide no input' correctly confirms the parameterless contract rather than contradicting it.

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 action (inspect standings/leaderboard) and states what comes back (ranked real agents, with demo and test guests separated). However, 'compare an agent's passport status' overlaps conceptually with the sibling resort_passport without explaining how this tool differs from it, so the agent gets no clear routing signal among siblings.

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?

'Provide no input' tells the agent how to invoke it, but there is no when-to-use guidance, no prerequisites, and no reference to any alternative tool such as resort_passport to disambiguate the overlap the description itself introduces.

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