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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the bar is lower. The description adds real context beyond them: it scopes the read to 'the connected renter' (i.e. the authenticated account only) and enumerates the exact returned state, which matters because there is no output schema. It still says nothing about behavior when no account is connected.

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 leads with the most decision-relevant fact (plan: free or paid) and then packs the remaining returned fields without filler. Every clause maps to content the agent or user will actually receive.

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 no input parameters, no output schema, and annotations carrying the safety profile, the description's field enumeration is the main source of return-value information and covers it well. It stops short of covering edge cases such as an unconnected/unauthenticated state or what the manage link requires.

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 per the rubric the baseline is 4. Schema coverage is nominally 100% and there is nothing for the description to disambiguate beyond the implicit 'no arguments needed' contract.

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 uses a clear verb ('Show') on a specific resource (the connected renter's account) and enumerates exactly what that resource comprises: plan, alert state, market, frequency, channel, and manage link. It is unambiguous on its own, but it never distinguishes itself from siblings such as set_apartment_alerts or update_search_preferences, which touch overlapping concepts (alerts, search settings).

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: the field list makes it obvious this is the tool for viewing account state, and the mention of the alerts on/paused flag faintly gestures at set_apartment_alerts. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the routing.

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