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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the required write scope, which annotations do not carry.

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 with zero filler, and the purpose is front-loaded ahead of the scope requirement. It is efficiently structured, though it is arguably under-developed rather than a model of well-packed conciseness.

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 an 8-parameter mutation tool with a nested 'defects' object and no output schema, the description covers purpose and auth but says nothing about the returned record, whether the inspection feeds the asset condition score, or how defects/attachments are handled. Adequate but with clear gaps against the tool's complexity.

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% (all 8 properties documented, including the nested defects object), so the schema carries the parameter load. The description adds no syntax, format or validation detail beyond what the schema already states, making the baseline 3 appropriate.

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+resource: 'Record an inspection against an infrastructure feature.' This clearly distinguishes it from the many sibling create_* tools, though it never names the closest alternatives (create_asset_condition_assessment, create_infrastructure_asset_comment) to reinforce the boundary.

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?

It gives one useful precondition — the required 'infrastructure_asset_inspections:write' scope — but offers no guidance on when to record an inspection versus a condition assessment, nor any mention of validation requirements beyond the scope.

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