get_psc_individual_full_record

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

No annotations are provided, so the description must carry the full burden. The description merely states 'Get individual PSC full record' without disclosing any behavioral traits such as what 'full record' includes, authentication requirements, rate limits, or error handling. This is insufficient transparency.

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 a single sentence with no wasted words, but it lacks structure and front-loading of key information. It is minimally concise but does not effectively convey the tool's purpose in a structured manner.

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 complexity of the domain (many similar sibling tools) and the absence of annotations and output schema, the description is highly incomplete. It fails to clarify what a 'full record' entails, how it differs from other PSC records, or what data to expect in the response.

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 input schema descriptions for the two parameters are basic but adequate ('The PSC ID', 'The company number'). Schema coverage is 100%, so the description adds no additional value beyond what the schema already provides. Baseline score of 3 is appropriate.

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 'Get individual PSC full record' with a specific verb and resource. However, it does not differentiate from sibling tools like get_psc_individual or get_psc_individual_beneficial_owner, which are also related to individuals. The lack of explicit distinction lowers the score from a 5.

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 guidance on when to use this tool versus alternatives. Given the numerous sibling PSC tools (e.g., get_psc_individual, get_psc_individual_beneficial_owner, get_psc_individual_verification), the description provides no context for selection, resulting in a low score.

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