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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the detection methodology (which headers and assets are inspected), but says nothing about whether the scan is passive/non-destructive, whether it issues live requests to the target, rate limits, or error behavior for unreachable hosts.

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?

One front-loaded sentence that leads with the action and resource before the CVE/CVSS detail. It is dense but every clause carries information; the CVSS score and CVE identifiers could arguably be trimmed for an agent that only needs to pick the tool.

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 no annotations and no output schema, the description is the only source of behavioral information, and it omits what the scan returns (a verdict, a report, a boolean exposure flag) and whether the probe is safe to run against production hosts. It is adequate for selecting the tool but incomplete for invoking and interpreting it.

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% and the single 'url' parameter is already documented in the schema, including an example format. The description adds no syntax, constraint, or format detail beyond what the schema states, so the baseline of 3 applies.

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 names a concrete action (inspects a website URL), the resource it examines (PHP runtime signatures such as X-Powered-By, Server, WordPress cookies/assets) and the outcome it produces (exposure evaluation for PHP2Shell). The scan verb is distinct from the sibling verbs convert_php_site_to_nextjs and get_php2shell_remediation_guide, but the description never names or contrasts those siblings, so differentiation is inferred rather than stated.

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 statement of when to run this scan versus fetching the remediation guide, no prerequisites (e.g. target reachability, permission to probe a host), and no exclusions. The only guidance is implicit in the verb 'inspects', which is not enough to route an agent confidently between scanning and remediation.

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