get_record_partial

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

No annotations are provided, so the description carries the full burden. It only states 'partial (lighter) record' without explaining what is omitted, performance implications, or any side effects. This is insufficient for an agent to understand behavioral traits.

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 description is extremely concise with two sentences for purpose and a separate line for each parameter. It front-loads the core purpose and avoids any unnecessary fluff.

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?

Given the presence of an output schema, return values are likely covered. However, the description lacks context about when to use this over 'get_record,' what constitutes 'partial,' and any performance or completeness trade-offs. It is adequate but not comprehensive.

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?

The schema description coverage is 0%, but the description adds meaning for both parameters: 'country_code: ISO 3166-1 alpha-2 country code (e.g. "GB").' and 'unique_id: Infobel unique ID for the business.' This goes beyond the schema's mere type and required status.

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 clearly states the tool's purpose: 'Get a partial (lighter) record for a business.' It specifies the verb 'Get' and the resource 'partial record for a business,' distinguishing it from the sibling 'get_record' by emphasizing 'partial.'

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?

The description implies that this tool is for lighter data compared to 'get_record,' but it does not explicitly state when to use this over alternatives, nor does it mention any when-not-to-use scenarios or prerequisites.

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