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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety and repeat-safety profile is covered. The description adds that the tool works on a 'small selected set' (a usage constraint) but doesn't disclose return size, rate limits, or behavior when nodeTypes aren't found.

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 the core purpose and followed by the gating condition. Every clause earns its place with no redundancy.

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 read-only detail-retrieval tool with no output schema, the description covers the essentials: what is returned, the scope of nodeTypes, and the required call sequence. The only real gap is the unexplained 'limit' parameter, which keeps it short of a 5.

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 must carry the load. It clarifies that nodeTypes are RFIX node-type identifiers and should be a 'small selected set,' but it never explains the 'limit' parameter (default 8) or the array format, leaving half the parameters 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 (Return) and resource (full parameter schemas and add-node templates) scoped to RFIX nodeTypes. It names the sibling rfix_search_block_catalog, so an agent can distinguish it from the other rfix_* tools without opening any 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?

The second sentence gives an explicit prerequisite and ordering: 'Call this only after rfix_search_block_catalog has narrowed the relevant blocks.' This tells the agent both when to use it and what must precede it, leaving nothing to inference.

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