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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds the useful mechanic that matching is driven by the stored company profile rather than only keywords, but says nothing about result ordering, pagination, or what 'open' excludes.

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, front-loaded with what the tool returns and how matching works, then the usage cue. The colon-plus-value construction is slightly dense but every clause carries information.

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 simple two-param read tool this is close to adequate, but with no output schema the description should hint at the return shape (list of tenders, ordering, how many) and it does not. The limit/pagination story is likewise absent.

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 coverage is 0% and the description clarifies only `query` ('a search phrase if given'), correctly signalling it is optional. The `limit` parameter (default 8, max 10) is never mentioned, so roughly half the parameters remain undocumented in both places.

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?

Names a specific resource (open tenders for the user's company) and the mechanism that produces them (the askTender profile's stated capabilities, or a search phrase). This distinguishes it conceptually from the generic search_tenders, though it never names that sibling 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?

Gives a clear trigger: 'Use when the user asks which tenders suit or match their company.' It states the context positively but offers no exclusions or explicit alternative (e.g. 'use search_tenders for keyword discovery across all companies'), so the agent must infer the boundary.

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