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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is lifted; the description adds genuinely new behavior: paging semantics, that the response carries the exact total, and that an empty list or null bound means the profile does not set that criterion. These are non-obvious semantics an agent could not get from the annotations.

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?

Front-loads the resource and its fields, then adds the edge-case semantics and paging in short clauses. It is dense but every clause (CPV/NUTS, value band, keyword whole-word matching, use case) earns its place. The parenthetical is long but informative rather than redundant.

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?

There is no output schema, so the description must describe return values, and it does so thoroughly: the criteria fields, the use case enum values, the active flag, and the total. Combined with the edge-case semantics, an agent has everything needed to interpret a response.

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?

Schema description coverage is 100%, so limit and offset are fully documented (defaults, max) in the schema itself. The description only restates 'paged with limit and offset' and adds the total-count behavior, adding little beyond structured data. Baseline 3 is correct.

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+resource ('the caller team's live tender profiles') and enumerates the fields each profile carries, so an agent knows exactly what this returns. It does not, however, name or contrast itself with the obvious siblings (tender_matches, tender_export_preview), so sibling differentiation is left to inference from the word 'profiles'.

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?

There is no when-to-use, when-not-to-use, or alternative routing. The description only says what a profile contains, never why an agent would call this versus tender_matches or tender_export_preview. Usage context is entirely unstated.

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