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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the scope of what is read (entity types, semantics, relationships, lifecycle states) but does not disclose return format, size, or whether it reflects a static snapshot. With annotations covering the key behavioral traits, a 3 is appropriate.

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 names the resource and lists the four content categories. Every word earns its place; there is no filler or repetition of the title.

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 parameterless read-only tool with strong annotations, the description is nearly complete. It tells the agent what content to expect, which is the main thing needed to decide to call it. It does not describe the output structure, but there is no output schema and the tool is simple enough that the absence is a minor gap rather than a critical one.

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 no parameter semantics burden. The description compensates by explaining what the ontology contains, which is the only meaningful semantic context for a parameterless read tool. Baseline 4 for zero parameters is correct.

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 tool reads the FLOCORE ontology and enumerates the specific content it provides: entity types, semantic meaning, allowed relationships, and lifecycle states. The verb 'read' is specific and the resource is named, distinguishing it from sibling tools that inspect, ask, create, or list other things.

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 this is the tool to use when an agent needs ontology-level knowledge about FLOCORE entities, relationships, and lifecycle states. It does not explicitly name alternatives or state when not to use it, but the context of sibling tools (e.g., flocore_ask, flocore_recall) makes the use case reasonably clear. A small gap is the lack of explicit routing guidance versus flocore_ask or aegis_inspect.

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