get_psc_super_secure_beneficial_owner

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Get ... details', implying a read operation, but does not specify expected output format, authentication needs, or any side effects. More detail is needed for safe invocation.

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, short and free of fluff. It is appropriately concise for a simple retrieval tool, though it could benefit from slightly more context without becoming verbose.

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 many sibling tools and no output schema, the description is incomplete. It does not describe the return format, what constitutes a 'super secure' beneficial owner, or how the parameters relate. More context is needed for effective use.

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 coverage is 100% with descriptions for both parameters (company_number and super_secure_id). The description adds no extra meaning beyond the schema, so baseline 3 is appropriate. However, it does not explain what a 'super_secure_id' is or how to obtain it.

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 beneficial owner details' specifies a verb and resource, but it does not distinguish this tool from sibling PSC tools like get_psc_individual_beneficial_owner or get_psc_corporate_entity_beneficial_owner. The term 'super secure' is not explained, leaving ambiguity about its unique purpose.

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 guidance is provided on when to use this tool vs. alternatives. Given the many similar PSC tools, the description should clarify the context (e.g., 'Use this for super-secure owners registered under specific regulations') but offers nothing.

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