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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false. The description adds meaningful behavioral context beyond them: the answer is 'grounded only in that document,' which tells the agent not to blend in other sources. It does not address why idempotentHint is false, but with annotations covering safety this is a solid addition.

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 tight sentences with the core scope statement front-loaded. The second sentence partly restates the first ('a specific file the user names' vs 'ONE of the user's documents'), costing a little density.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. Scope, grounding, and usage condition are all covered for a two-parameter, fully-documented query tool.

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 100%, so both parameters are already documented by the schema. The description reinforces that the question is about the named file but adds no syntax, format, or size guidance beyond the schema, so baseline 3 applies.

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 (answer/find) and resource (a Xenition document) with an explicit scope constraint: 'ONE of the user's Xenition documents' grounded only in that document. The 'ONE' scoping and 'a specific file the user names' cleanly separate it from workspace-wide siblings like ask_workspace.

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 a clear when-to-use condition: 'Use to look something up in a specific file the user names.' It does not name an alternative tool or state exclusions, so it stops short of full routing guidance, but the selection condition is unambiguous.

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