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

No annotations were provided, so the description carries the full burden. It does disclose a useful behavioral trait not available elsewhere: '2 point per returned record,' which tells the agent about cost, and it names the underlying source portal. But it omits auth requirements, rate limits, and pagination behavior beyond the schema, leaving meaningful gaps for a no-annotation tool.

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?

A single, front-loaded sentence that identifies the action, source, and lookup key before trailing off into output fields and a pricing note. Compact and efficient, though the trailing '2 point per returned record' fragment is slightly abrupt.

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 annotations and no output schema, the description partially compensates by enumerating return fields, which is genuinely helpful. However, it lacks usage routing against the many sibling company tools and omits behavioral details an agent would need, so it is only minimally complete.

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%, with keyword, max_items, and start_page all documented in the schema, so the baseline is 3. The description lists returned fields (name, NIF/NIPC, municipality, date/type of newest publication) rather than adding meaning to the input parameters, so it does not exceed the 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?

States a specific verb and resource: 'Search the Portugal company registry (Registo Comercial publications portal) by entity name.' An agent immediately knows what the tool does and the data source. However, it does not distinguish itself from the sibling run_pt_companies or run_pt_company_filings, so the agent must infer the difference.

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 guidance and no mention of the closest alternatives (run_pt_companies, run_pt_company_filings). With ~150 sibling search tools, routing depends on explicit differentiation, and this description provides none.

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