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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds minimal behavioral context beyond stating that the details are 'public', which is useful but does not disclose additional traits like data freshness or authentication needs. It does not contradict 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?

The description is a single sentence, front-loaded with the action ('Return'), and contains no filler. Every word adds value, precisely naming the entity and the expected data fields.

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 contact info tool with no parameters and no output schema, the description fully captures what the tool returns and for which entity. The annotations cover safety, and the description leaves no critical gaps in understanding.

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 tool has zero parameters, so the input schema is trivial and the description does not need to explain any. Baseline for 0 parameters is 4, and the description appropriately makes no parameter claims. It adds no parameter information because none exists.

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 the verb 'Return' with a specific resource ('public contact details of SCA Zandomeni — Timișoara') and enumerates the fields (phone, email, website, service area). It is unambiguous and easily distinguished from sibling tools that handle blog posts or expertise areas.

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?

The description implies usage: use this tool when you need contact details for SCA Zandomeni. However, there is no explicit mention of when to use this tool over alternatives or any exclusions. Sibling tool names provide some context, but the description itself does not offer direct guidance.

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