x3d_search_nodes

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

No annotations are provided, so the description must carry the full burden. It mentions searching both node names and descriptions in the X3D 4.0 spec, which adds useful behavioral context. However, it does not disclose any additional behaviors such as result limits, sorting, or side effects, leaving it at a basic acceptable level.

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?

The description is concise and well-structured: a clear purpose sentence, a usage guideline, and a compact parameter explanation. Every sentence serves a purpose with no filler.

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?

This is a simple single-parameter tool with an output schema present, so the description does not need to explain return values. It adequately covers what the tool does and when to use it, leaving little ambiguity. A 5 would require more behavioral detail, but the context is sufficiently 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?

The input schema has no description for the 'query' parameter (0% coverage). The description compensates with an Args section that provides a definition and multiple examples ('light', 'texture', 'animation', etc.), adding significant value beyond the schema.

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 clearly states 'Search for X3D nodes by name or description' with a specific verb and resource. It also differentiates from siblings by indicating this is for when the exact node name is unknown, which distinguishes it from x3d_node_info.

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?

Explicitly provides a condition for use: 'Use this when you don't know the exact node name.' This gives clear context but does not name specific alternative tools or exclusion scenarios, so it falls slightly short of a 5.

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