get_psc_statement

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

With no annotations, the description must disclose behavioral traits. It only states 'Get PSC statement details' but does not indicate whether this is a read-only operation, any permissions required, or what the response format looks like. The lack of any side-effect or safety information is a significant gap.

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 brief (single sentence) but lacks necessary details. While conciseness is valued, it comes at the expense of completeness, making the tool harder to use effectively.

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?

The description is insufficient given the context: no output schema, two parameters that are not explained in the description, and many sibling tools. The user is left to infer how to obtain a statement_id and what the response contains.

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%, so the input schema already describes both parameters (statement_id and company_number). The description adds no additional meaning beyond what the schema provides, hence baseline 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 it retrieves details of a specific PSC statement, distinguishing it from the sibling tool get_psc_statements_list which returns a list. The verb 'Get' and resource 'PSC statement details' is specific, though it could be more explicit about what 'details' entails.

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 versus alternatives such as get_psc_statements_list or other PSC-related tools. There is no mention of prerequisites, such as needing a statement_id from a prior call, nor any exclusions.

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