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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds genuine behavioral value by promising a lightweight payload that omits full parameter schemas, explaining why this call is cheap and safe to run before building an action. It omits result-count, ranking and empty-result behavior.

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, no waste: capability first, then the call sequence. The key scoping fact (no full schemas returned) is front-loaded rather than buried.

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?

There is no output schema, so the description must characterize the return shape, and it does so at a high level (catalog summaries, not full schemas) while naming the exact follow-up tool. Missing lower-limit details on result size and ordering keep it short of fully complete.

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%, so the description carries the burden. It clarifies the query parameter's expected syntax ('natural-language keywords' rather than IDs or regex), which is genuinely useful, but says nothing about limit (default 12) or what a null query returns, leaving one of two parameters fully undocumented.

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 and resource ('Search concrete RFIX node types') plus scope ('by natural-language keywords') and output shape ('without returning full parameter schemas'), which cleanly separates it from rfix_get_block_details. It does not, however, distinguish itself from the sibling rfix_list_blocks, so an agent must infer that difference.

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?

Gives an explicit workflow: use this before constructing add_node actions, then call rfix_get_block_details for the selected nodeTypes. That is real when-to-use and follow-up guidance. It lacks any when-not-to-use clause (e.g., when the node type is already known and get_block_details should be called directly).

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