find_by_qualified_name

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

Annotations are absent, so the description carries the full burden. It does not disclose whether the operation is read-only, how errors are handled (e.g., not found), or any side effects. While 'find' implies a read, nothing about failure modes or performance is provided.

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?

A single sentence that is front-loaded with the core purpose and includes an example. No redundant words or repetition.

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 single-parameter lookup with an output schema present, the description is nearly complete. It conveys the input format and purpose. It could mention whether a missing element throws or returns null, but the output schema likely covers the return type.

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 compensate. It does add meaning by giving a concrete format example ('Model::Package::Block'), which clarifies the expected delimiter and structure. However, it does not explain case sensitivity, escaping, or edge cases.

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 states a specific action ('Find an element') with a clear resource ('fully-qualified name') and provides an illustrative example. It distinguishes itself from siblings like find_by_name and find_by_type by emphasizing the fully-qualified format.

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?

There is no guidance on when to use this tool versus alternatives such as find_by_name, find_by_type, or search. The purpose implies its use when a fully-qualified name is known, but no explicit selection criteria or exclusions are given.

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