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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and idempotency profile is covered. The description adds scope exclusions (no execution/enrollment/payment), but says nothing about return content or openness beyond what the annotations state.

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 with no filler, and the scope exclusions are stated up front after the resource list. Efficient, though the resource enumeration itself is vague rather than wasteful.

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?

With no output schema and no parameters, the description carries the burden of explaining what is returned, and it does not describe the shape or nature of the 'rules' or 'projects' it reads. For a zero-param tool whose annotations already cover safety, this is adequate but leaves the resource under-defined.

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 takes zero parameters, so the 4 baseline applies. The description adds no parameter information, which is appropriate since the schema has no properties to document.

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 verb 'read' is clear, but the resource is muddled: the tool is named read_engines yet the description enumerates 'distributed investigation projects, local demo and result submission rules' without ever defining what an 'engine' is or how these items relate. There is no differentiation from the many sibling read_* tools.

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 clause 'No job execution, enrollment or payment' establishes boundaries on what this tool is not for, which is a partial when-not signal. However it never states when an agent should choose this over alternatives like read_distribution_study or read_site_policy, leaving selection to inference.

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