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

Annotations already cover safety (readOnlyHint, openWorldHint=false), and the description adds genuinely non-obvious behavior: the catalog requires no model loaded, and it spans both analysis results and /db model tables. It does not discuss ordering, size of the catalog, or rate limits, but nothing contradicts 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?

Purpose and returned fields are front-loaded, and the filter/caller guidance closes the description. The long parenthetical enumeration of result categories ('reactions, displacements, beam/truss/plate/solid forces…') is dense but earns its place by telling the agent what coverage to expect; it is slightly longer than strictly needed.

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 no output schema, the description carries the return shape itself (id, TABLE_TYPE or /db endpoint, components, arguments) and explains the pre/post split and free-text matching. For a zero-required-parameter catalog with full schema coverage, nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and each parameter already documents itself (scope enum, search examples, id). 'Filter with scope, search or id' restates the schema rather than adding semantics such as how scope interacts with search or what happens when both are passed, so the baseline 3 applies.

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?

Opens with a specific verb and resource: 'Lists the CIVIL NX tables the Bulk Tabular Result Exporter plugin can export', then enumerates the returned fields (id, TABLE_TYPE/db endpoint, components, arguments). The two calling siblings, preview_result_table and export_result_tables, are named, so the agent can place it in the workflow without opening the 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?

'Use it to pick the table id for preview_result_table and export_result_tables' gives explicit downstream routing, and 'Needs no model' sets the precondition. It stops short of stating when not to use it (e.g. when the table id is already known), so it is clear context rather than a full when/when-not rule set.

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