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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only added behavioral claim is 'bounded', which hints at truncation/limits but never says what the bound is, whether results are paginated, or what happens with no matches. Adequate, but it adds little beyond the annotations.

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 sentences, zero padding, with the scoping constraint front-loaded before the alternative-tool pointer. Every clause earns its place.

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 read-only, single-purpose log reader with no output schema and full schema coverage, the description plus annotations give an agent what it needs to call the tool. It is slightly thin on what the returned log window looks like (e.g., default tail of 100, build vs runtime source semantics), though those live in the schema defaults.

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 every parameter (grep, tail, since, source, service, project_id) is already documented in the schema, including the 'never its name or slug' rule. The description only restates the project-ID immutability and single-service scoping, adding no new syntax or semantics. Baseline 3 is correct.

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 ('Read bounded logs'), plus the scope constraints ('one service within a project', selected by immutable project ID). It also names the sibling it is not (nerdit_diagnose_project), so an agent can route without opening either schema.

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?

Gives an explicit alternative for a concrete scenario: 'Use nerdit_diagnose_project when a deployment fails.' However it offers no guidance on when NOT to use this tool, and no prerequisites (e.g., which ID to supply, whether the project must be running) beyond what the schema already states.

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