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

No annotations are provided, so the description carries the full burden. It does disclose one useful contract detail (the returned version must be echoed back as termsVersion), but says nothing about whether this is a read-only call, what the return shape or size is, or any auth/rate constraints.

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 tight sentence with no filler, and the round-trip hint is embedded rather than buried. It is slightly cryptic as an unverbed fragment, which keeps it out of the top band.

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 output schema and no annotations, the description should explain what actually comes back (clause list, version identifier, profile field inventory) and how to use it. Instead it gestures at the contents in one ambiguous clause, leaving the agent to guess at the return structure and the intended call sequence.

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 the schema is empty, so there is nothing for the description to clarify. Baseline for a no-argument tool.

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 the resource (listing terms/clauses plus profile fields) but is a noun phrase with no verb, so the agent must infer it is a retrieval tool. It is roughly distinguishable from siblings like listing_describe or listing_draft, but the phrasing 'the clauses a listing is judged by' is indirect enough that an agent could confuse it with a schema/validation endpoint.

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 parenthetical 'send it back as termsVersion' hints at a workflow, but there is no explicit when-to-use statement, no prerequisites, and no named alternative among the many sibling tools. The agent has to reconstruct the calling context itself.

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