get_psc_super_secure

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

With no annotations, the description carries full burden. It only says 'Get super secure person with significant control' which provides no behavioral traits—no mention that it is a read operation, no explanation of authorization needs, rate limits, or return value specifics. This is critically insufficient.

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 short (one sentence) but not appropriately informative. Conciseness is not valuable when it sacrifices clarity and utility. The sentence does not earn its place as it adds minimal new 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?

Despite having 2 simple parameters and no output schema, the description is wholly inadequate. It does not explain the nature of the data returned, the significance of 'super secure', or how this fits with other PSC endpoints. For an agent, this offers no decision-making context.

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%, providing basic descriptions for both parameters. However, the tool description adds no additional meaning beyond the schema. A baseline of 3 is considered, but the description fails to add value; for example, it could clarify the 'super_secure_id' is a unique identifier. Hence a score of 2 reflects the poor contextual enhancement.

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 'Get super secure person with significant control' is essentially a tautology of the tool name. It does not explain what 'super secure' means or how this tool differs from sibling tools like get_psc_individual or get_psc_super_secure_beneficial_owner. The purpose is only vaguely conveyed.

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?

No guidelines are provided. There is no indication of when to use this tool versus the many other PSC-related tools, nor any prerequisites or context about access to 'super secure' data.

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