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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description adds real context beyond them: it discloses an authentication prerequisite ('Needs the askTender account connected') and outlines the returned assessment (requirements met, gaps, remediation). It stops short of stating error behavior when the account is not 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?

Two sentences with essentially no waste; the capability statement is front-loaded and the usage trigger follows. There is mild redundancy between 'can bid on a tender and qualifies' and the later 'qualifies for, or can bid on'.

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, the description usefully enumerates what is returned (which requirements are met, what is missing, how to close each gap) and flags the account prerequisite. The one material omission is disambiguation from the sibling can_company_bid, given only one fully documented input parameter otherwise.

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?

Only one parameter, tender_id, and schema description coverage is 100%, so the schema already carries the semantics. The description adds no format or constraint detail beyond 'a specific askTender tender,' which is the expected baseline when the schema does the work.

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 and resource: assessing the user's own company against a given tender and reporting which requirements are met, which are missing, and how to close gaps. It clearly scopes to the user's own askTender-account company. However, it never distinguishes itself from the near-identical sibling can_company_bid, leaving the agent to guess which one to select.

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 an explicit trigger: 'Use when the user asks whether their own company qualifies for, or can bid on, a specific askTender tender.' The 'own company' phrasing hints at a contrast with can_company_bid, but no alternative or exclusion is actually named, so the boundary between the two tools is left to inference.

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