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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the main safety profile. The description adds the "public" aspect and "before contacting" context, but these are largely implied by the tool name and do not disclose substantial behavior beyond what annotations provide. The description does not mention response format, pagination, or access controls.

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, front-loaded sentence that states the action (Return), the resource (public pages), and the use context (before contacting COTRUGLI). No filler or redundant phrasing, and it earns its place for a simple read-only tool.

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 0-parameter, read-only tool with no output schema, the description conveys the core purpose and usage timing. It is slightly ambiguous what exactly constitutes a "public page" (URLs, endpoint names, titles), and no return structure is described, hence not a 5. Still, the tool is simple enough that the description is largely sufficient.

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 there is nothing for the description to clarify beyond what the empty schema already shows. Baseline is 4 for no-parameter tools; the description does not need to add parameter semantics.

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 uses a specific verb ("Return") and names the exact resource ("public pages") along with the intended audience and timing ("before contacting COTRUGLI"). This clearly differentiates it from sibling tools like get_opportunity or list_opportunities, which target different resources.

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 phrase "before contacting COTRUGLI" establishes a clear workflow context for when to call this tool. It does not name alternatives or explicitly exclude siblings, but the context is specific enough that an agent can infer this is for pre-contact information gathering rather than other operations.

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