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

With no annotations provided, the description carries the burden. It discloses that sessions are public and details what data is returned, which is helpful. The verb 'Fetch' implies a read-only operation, but it does not explicitly state the absence of side effects, leaving a minor gap.

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 first two sentences are concise and useful, but the third sentence contains an open research question that is irrelevant to tool selection or invocation. This extraneous content prevents a higher score for conciseness.

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 get tool with one parameter and no output schema, the description is fairly complete: it lists the returned data and notes the public nature of sessions. It lacks error-handling details and the irrelevant open question adds noise, but overall it adequately covers the essentials.

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 only parameter, flock_id, is not explained in the description. The schema provides only minLength and no description, and schema coverage is 0%. Since the description does not compensate by defining flock_id or providing format details, it adds no value beyond the parameter name.

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's function with a specific verb ('Fetch') and resource ('full current state of a flock session'), enumerating the contents (parameters, tick, latest metrics, complete history of parameter changes). This distinguishes it from siblings like flock_step or flock_set_params.

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 line 'Sessions are public — you can pick up where another agent left off' provides clear context for using the tool to retrieve a session's state. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full guidance.

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