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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false). The description adds value beyond those by disclosing the curated, closed scope ('explicitly selected') and the access requirement ('require no account'), telling the agent no authentication is expected. No contradiction with annotations.

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 compact sentences, both information-bearing: the first states the verb and scope, the second adds a boundary exclusion. Nothing is wasted and the action is front-loaded.

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 zero-parameter listing tool, the description adequately covers scope ('technical resources'), access ('no account'), and the key exclusion ('community posts'), which is enough for an agent to select and invoke it correctly. The only minor gap is the absence of output shape, which is acceptable given no output schema and the closed-world annotation.

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?

With zero parameters and an empty schema, the baseline of 4 applies. Schema description coverage is trivially 100%, and the description correctly focuses on operation and scope rather than padding parameter detail.

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 verb ('Find') over an explicit resource class: 'explicitly selected technical resources that require no account.' The exclusion 'Does not enumerate community posts' adds a scope boundary beyond the title, though it does not name sibling tools for direct contrast. This is clear and specific, just short of full sibling differentiation.

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?

'Does not enumerate community posts' provides a when-not signal, and 'require no account' implies this tool is for public, credential-free lookups. However, no alternative tool is named and no condition for choosing trustverum_read_resource or trustverum_access_policy is given, so usage guidance is implied rather than explicit.

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