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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds a plan-tier authorization requirement not present in the structured fields, but says nothing about result size, ordering, or coverage limits.

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, zero waste. The core definition is front-loaded and the eligibility constraint is appended as a compact qualifier rather than buried in prose.

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-only list tool the description is close to sufficient, and the plan gate is an important addition. However, with no output schema, an agent gets no signal about what a renewal record contains (deadline, buyer, value) or how many results to expect.

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 an empty object, so there is no parameter semantics to document. The description correctly implies the scope is implicitly the calling user's markets, which is the only semantic an agent needs.

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 concrete resource and scope: contracts in the user's markets that end soon, with a parenthetical clarifying the renewal/tender framing. It is clearly distinct from sibling list tools like my_bids or my_saved_tenders, though it never names an alternative explicitly.

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 only usage guidance is the eligibility gate ('Intelligence plan and above'), which is genuinely useful but is a prerequisite rather than a when-to-use rule. It never says when to prefer this over my_matching_tenders, my_watchlist, or search_tenders, so the agent must infer the trigger from the name alone.

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