TrustScan

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose what the scan checks for, but it does not explicitly state whether the file is modified, what permissions are needed, or how findings are returned. The scan wording implies read-only behavior, but this is not explicit.

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, front-loaded sentence that immediately identifies the action, target, and scan categories. Every word adds value and there is no redundant or filler content.

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?

With one required parameter and an output schema present, the description covers the core purpose and scope well. It lacks explicit usage guidance against the sibling, but that gap is already accounted for in the usage dimension and does not make the tool difficult to invoke correctly.

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 has 0% description coverage and only one parameter, filepath. The description adds that the parameter refers to a single file to scan, but it does not explain path formats, file types, or any constraints on the filepath.

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 states a specific action ('security scan'), a clear target ('a single file'), and the scan scope (invisible Unicode, dangerous patterns, secrets). It also distinguishes itself from the sibling trust_scan_server by focusing on a single file rather than a server.

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 phrase 'a single file' and the sibling name trust_scan_server imply a file-level versus server-level use case, but the description does not explicitly state when to use this tool over the sibling or provide any exclusion conditions.

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

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

With no annotations, the description carries the full burden of disclosing behavior. It only says 'Security scan', which is vague and does not indicate whether the operation is read-only, what it checks, whether it has side effects, or any other behavioral details. The description adds no context beyond the tool's name and basic purpose.

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, front-loaded sentence that immediately states the action and target. There is no filler or unnecessary detail, making it highly efficient and easy to parse.

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 simple two-parameter schema and the presence of an output schema (not detailed here, but noted in context), the description is sufficient for the agent to understand the tool's purpose and how to invoke it. It could benefit from a brief note on what the scan returns, but that is covered by the output schema.

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 already provides descriptions for both parameters (path and package_name) with 100% coverage, so the description adds no additional meaning beyond what is in the schema. The baseline of 3 applies because the schema fully documents the parameters and the description does not expand on them.

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 states a specific action ('Security scan') and a clear resource ('an MCP server or skill package'), which distinguishes it from the sibling tool trust_scan_file that likely targets files. It is concise and unambiguous, though it does not explicitly contrast with the sibling.

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 phrase 'before trusting it' provides a general usage context, but there is no explicit guidance on when to use this tool versus trust_scan_file or any other alternative. The description implies a pre-trust evaluation but leaves the choice criteria to the agent.

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