check_environment

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the full output contract (`ready`, `tools.<name>` fields, `project_root`), the constraint that the agent cannot run the install command itself, and that project_root is the only readable/writable directory with all other paths relative to it. This is unusually rich operational context.

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?

Front-loads the imperative ('Check that ...') and the ordering rule ('Call this FIRST'), then organizes the rest into a scannable Output: list. Because no output schema exists, the return-value detail is load-bearing rather than padding.

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 input parameters and no output schema, the description carries the full burden and meets it: it documents the readiness flag, per-tool fields, failure remediation, and the project_root scoping rule. An agent has everything needed to invoke it and act on its result.

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 tool takes zero parameters, so the baseline is 4. The description does add useful contextual semantics about the environment it inspects (project_root as the write scope, tool version minimums), but there are no parameters whose meaning could be clarified.

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?

States a specific verb and resource: verifying that the BPP command-line tools are installed and sufficiently recent, and names the exact tools checked (bpp-seqs, bpp-tree, bpp-lint, bpp-docs, bpp). This clearly distinguishes it from sibling tools that operate on data, trees, or control files.

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?

Explicitly instructs 'Call this FIRST in every session, before any other tool', and explains what to do when the check fails (read `problems`, tell the user the exact `install_hint` command). It also names the alternative path for setting a project (set_project or BPP_MCP_ROOT) when project_root is null.

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