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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious context: it is free during beta, coverage is country-dependent (Portugal gets entered contests, win rate, rivals, losses), and it instructs the agent to report facts rather than conclusions about wrongdoing — a real usage constraint beyond the structured fields.

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?

The opening "Free during beta" is a weak lead for a data-retrieval tool, and the middle is one very long run-on sentence packing a dozen output fields. The field inventory is useful given there is no output schema, but the wall-of-text structure hurts scannability and front-loading.

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 and flags the country-specific depth of Portuguese data, which is exactly what an agent needs to set expectations. It still omits ambiguity handling (multiple name matches), result limits/pagination and whether absence of data is possible, which are relevant for a 3-param search tool.

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 company, since and countries are already documented in the schema (including the NIF example and the 'part is fine' hint). The description only restates name/tax-id search and does not explain the since or countries filters or how they interact, so it adds little beyond the schema baseline.

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 states a specific verb-like purpose (profiling what a company wins in public procurement) and enumerates the concrete data returned: contracts, value, buyers, sectors, discount below estimate, rivals, losses. It is clearly a per-company profile tool, though it never explicitly distinguishes itself from the sibling award_history or match_company, leaving the boundary to inference.

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?

"Search by name or tax id (NIF)" gives a minimal how-to-invoke cue, and the profile framing implies it is the tool for company-level analysis. But there is no statement of when to prefer it over award_history, bid_intelligence or match_company, and no exclusions or prerequisites beyond the beta note.

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