Environment & Config Check

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows it's a safe read. The description adds behavioral detail about what is validated (lockfile freshness, tsconfig, Svelte config), making the tool's scope more transparent. It does not contradict annotations or disclose side effects, but the annotation coverage reduces the need for more.

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 two sentences plus a list of examples, all relevant. It front-loads the purpose and provides concrete example queries. No filler or redundancy.

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 tool has two simple optional parameters, no output schema, and good annotations. The description explains the validation scope and gives usage examples. It does not describe return format, but for a read-only validation tool this is acceptable.

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%: both 'project' and 'directory' have descriptions. The description does not add additional param semantics beyond the schema, so it relies on the schema. Baseline 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 clearly states the tool 'Validate project environments' and enumerates specific checks: .env/.env.example sync, lockfile freshness, tsconfig best practices, Svelte config, multiple lockfiles. This distinguishes it from sibling tools like depsonar_check or depsonar_audit, which focus on dependencies or vulnerabilities.

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 description provides context for when to use via example prompts like 'Check my project environments' and 'Any env issues in JobPin?', and implies this is for environment/config validation. However, it does not explicitly mention alternatives or exclusions compared to sibling tools, so it's clear but not fully explicit.

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