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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered without the text. The description adds real value beyond that by disclosing 'Results are filtered to your permissions', an access-control behavior the agent could not infer from the structured fields. It does not mention pagination or result ordering, though an output schema exists.

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, front-loaded with purpose then usage, with no filler. Every clause carries information the agent can act on.

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 an output schema present and full annotation coverage, the description need not explain return values or safety. It covers scope, triggers and permission filtering; the remaining gap is pagination behavior for limit/offset, which matters for a search tool but is secondary.

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% across three parameters, so the description must compensate. 'By name or description' usefully clarifies what the query string matches against, but limit and offset are left entirely undocumented beyond their schema types and defaults, so compensation is only partial.

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 gives a specific verb and resource ('Search all available engineering tools') plus the matching dimensions ('by name or description'), which is enough for an agent to know exactly what the tool returns. It stops short of naming a sibling alternative, but this is a meta-discovery tool whose siblings are domain tools rather than competing search entries, so the omission is minor.

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?

'Use this when a task crosses design, meshing, simulation, inference, documents or visualisation' gives concrete trigger conditions, and 'do not limit yourself to the current UI panel' tells the agent to widen scope beyond ambient context. There is no explicit when-not-to-use clause or named alternative, which keeps it below a 5.

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