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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), yet the description adds two genuinely useful facts beyond them: the daemon token must own the service, and a reader's reply omits variable names (a redaction quirk that affects interpretation of results). It stops short of describing cost, latency, or failure behavior.

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 tight sentences: the capability and its outputs come first, followed by the auth precondition and the result caveat. No filler, and every clause carries information the agent needs.

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 output schema, the description carries the burden of describing returns, and it does so (deploy phase, health, bounded logs, remediation) while also flagging the token ownership requirement and the omitted variable names. It is close to complete; only error/failure behavior is left unstated.

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 100%, so all three parameters are already documented with patterns, defaults, and bounds. The description only echoes that the project is addressed 'by immutable ID' and that logs are 'bounded', which reinforces but does not extend 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?

States a specific verb and resource ('Diagnose one service within a project') and enumerates the outputs (deploy phase, health, bounded logs, remediation), which implicitly separates it from the broader nerdit_get_project and nerdit_project_logs siblings. It never names an alternative explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied by the scope ('one service within a project') and by the prerequisite 'Requires the daemon token to own the service', which tells the agent a precondition. There is no explicit when-to-use/when-not guidance and no named alternative such as nerdit_project_logs for raw log retrieval.

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