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

Annotations already establish readOnly, idempotent, closed-world and non-destructive behavior. The description adds real context beyond them: the diagnosis is deterministic and derived from recorded evidence (not a live probe), and recovery suggestions are inert and execute nothing — a valuable warning for an agent tempted to act on them.

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?

Two short sentences, no waste, with the core purpose and the most dangerous misreading (that suggestions execute) front-loaded.

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?

There is no output schema, so the description should convey what the diagnosis returns; it mentions recovery suggestions but not the diagnosis content itself (status, failure reasons, evidence fields). For a two-required-param read tool with rich annotations this is adequate but incomplete.

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 0%, so the description must carry parameter meaning, and it adds nothing about projectId or deploymentId. The schema's regex patterns at least reveal the prj_/dep_ prefixes, but neither field's semantics or relationship is explained anywhere.

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 (read/diagnose) and resource (deployment), and the phrase 'from recorded deployment evidence' distinguishes it from a live probe. It does not name a sibling such as eurobase_get_deployment or eurobase_list_deployment_logs, so the differentiation is implied rather than explicit.

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?

No when-to-use or when-not guidance, and no alternatives are named. An agent can infer this is for diagnosing a deployment after a failure, but nothing says whether to prefer it over get_deployment or the log/event listing tools.

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