Search Ygdria notes by tag

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully pins down exact-match (non-fuzzy) semantics and subtree scoping, but says nothing about archived-note handling, result volume/pagination, or case sensitivity of tag matching.

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 well-formed sentence with the resource and the exactness constraint front-loaded; 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?

For a simple read-only lookup with annotations covering safety and no output schema, the description is close to sufficient. The remaining hole is includeArchived semantics and whether archived notes are silently excluded by default.

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 67% and the description restates the two documented parameters (exact tag, placement plus all descendants) without adding format or syntax detail. The third parameter, includeArchived, has no schema description and is never mentioned in the description, so its effect on results remains 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+resource ("Find notes with an exact Ygdria tag") and the optional scope. It never names or distinguishes itself from the obvious siblings search_notes and list_tags, so the agent has to infer the difference between exact-tag lookup and general note search.

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?

Usage is only implied by "exact Ygdria tag" and the optional placement subtree; there is no explicit statement of when to prefer this over search_notes, nor any exclusion such as "use list_tags to discover tag names first." Adequate but leaves routing to inference.

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