get_design_assessment

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that—no indication of what the assessment returns, whether it requires an existing baseline, or how state_id and baseline_state_id relate.

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?

Only four words, so there is no verbosity to trim, but the brevity is under-specification rather than concision. Nothing is front-loaded because nothing of substance is present.

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 tool with nested opaque objects, required state/baseline identifiers, no output schema, and no annotation detail about results, the description supplies none of the context needed to invoke it correctly. This is completely inadequate for 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 0%, and two of the most opaque inputs—basis and intent as untyped nested objects—are entirely undocumented in both schema and description. The description also provides no meaning for state_id or baseline_state_id, so it fails to compensate for the coverage gap.

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?

"get design assessment" merely restates the tool name with no added specificity: it does not say what a "design assessment" is, what it evaluates, or how it differs from siblings like design, get_change_review or get_validation_plan. An agent cannot distinguish this from adjacent review-oriented tools on the basis of the text.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling tools (design, get_change_review, get_validation_plan, review_context). The agent must infer everything from the name alone.

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