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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not mention side effects, return format, required context, or whether this is a read-only operation. The cost note is a billing detail, not a behavioral trait. This is a significant gap.

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?

The description is very short and front-loaded with the main verb and resource, which is good for conciseness. However, it is under-specified to the point of being a fragment rather than a well-structured explanation. It is not verbose, but it omits essential information, so it earns a middling score.

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?

Given the tool has one required parameter, no output schema, and no annotations, the description is critically incomplete. It fails to explain what 'dI/dt analysis' means, what the report contains, how 'assessmentId' is used, or any prerequisites. This is completely inadequate for an agent to correctly select and invoke the tool.

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?

The input schema has only one parameter, 'assessmentId', but the description does not mention it or explain its purpose. With schema description coverage at 0%, the description must compensate, but it does not. The parameter name alone is insufficient to convey how to use the tool effectively.

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?

The description clearly states the action ('Generate') and the resource ('a property-specific dI/dt analysis'), which is a specific deliverable. However, it does not explain the term 'dI/dt' or distinguish itself from sibling tools like 'get_information_theoretic_recommendation' or 'generate_energy_recommendation_preview', so it is clear but lacks sibling differentiation.

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 description provides no guidance on when to use this tool, when not to, or how it relates to alternatives. The only extra information is a cost note ($0.25/call), which is not usage guidance. This falls into the 'no guidance' category.

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