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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the description is not needed for the safety profile. It adds real, non-duplicated context: the returned data is a recorded snapshot rather than a live probe, which tells the agent about data freshness and that a stale or stopped deployment may still report state here. Return contents and error behavior are not described.

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?

A single front-loaded sentence with the read scope first and the behavioral exclusion second. No filler, nothing repeated from the title or annotations.

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 two-required-parameter getter with no output schema, the description should at least signal what 'recorded deployment state' contains (status fields, the evidence timestamps, maybe build metadata). It conveys the freshness caveat but leaves return shape and ID scoping unspecified.

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% and the description says nothing about projectId or deploymentId, so it does not compensate for the coverage gap. The only help is structural: the patterns (^prj_..., ^dep_...) tell an agent which ID form each slot takes, but the parent/child relationship between project and deployment is left unstated.

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') and resource ('recorded deployment state and evidence timestamps'), which is more precise than a plain 'get'. It does not name the sibling it is distinct from (e.g. eurobase_diagnose_deployment), so the boundary must be inferred from 'does not probe the runtime'.

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 clause 'does not probe the runtime' implies that live/health diagnostics belong to a sibling such as eurobase_diagnose_deployment, but no alternative is named and no when-to-use condition is stated explicitly. The usage signal is present only by negation.

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