Add declare(strict_types=1)

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

Adds context beyond annotations: clarifies it only adds if not present ('yoksa'), and describes dryRun preview behavior. No contradiction with annotations. Could explicitly mention file modification side effect, but destructiveHint covers that.

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?

Single, efficient sentence with no redundant words. Front-loads key action and parameter usage.

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?

For a simple idempotent file modification tool with no output schema, the description fully explains the operation, parameter usage, and preview mode. No missing information.

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?

Input schema covers 100% of parameters with descriptions. Description reinforces dryRun usage but adds little new meaning beyond the schema. 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?

Specific verb 'add' and resource 'declare(strict_types=1) to PHP file' clearly stated. Distinguishes from sibling PHP tools by focusing on a single, narrow operation.

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?

Description implies usage via context (add if missing, preview with dryRun) but does not explicitly state when to use or exclude alternatives. No direct siblings to compare, but could benefit from a note about prerequisites.

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