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

Without annotations or additional description, the tool's behavior is not transparent. It is unclear whether it performs a read-only operation, has side effects, or requires any authentication. The description does not disclose any potential impacts or constraints.

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 very short and to the point, which is efficient. However, the phrasing is terse and could benefit from a bit more detail to clarify its purpose, slightly reducing the score from a perfect 5.

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?

There is no output schema, and the description does not state what the tool returns (e.g., a JSON object with contact info and scope definitions). Without this, an agent cannot fully anticipate the response format or content, making the description incomplete.

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 no parameters, so the schema fully covers the input space. The description does not need to elaborate on parameters since there are none, earning a baseline score of 4.

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 'Contact and scope of this server' indicates the tool provides server information but lacks a clear verb or explicit statement of what is returned. It is somewhat vague and does not differentiate well from potential sibling tools without further context.

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?

No guidance is provided on when to use this tool versus the sibling tools (e.g., boe_day, tenders_search). The description does not mention any conditions or contexts where calling 'info' would be appropriate or preferred.

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