get_loop_status

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

There are no annotations, so the description alone must convey behavioral traits. It states that the tool 'returns' data, implying a read-only operation, but it does not explicitly confirm non-destructiveness, describe side effects, or explain session-scoped behavior details. The added scope 'in this server session' provides some context but not enough depth.

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, compact sentence that gets straight to the point without extraneous detail. It is front-loaded with the action and provides the essential resource and scope.

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?

Given the absence of an output schema and annotations, the description is the only source of information, yet it does not explain what 'looping' means, what the output structure looks like, or when to invoke this tool relative to siblings. The tool's simplicity is offset by the lack of contextual guidance, leaving the agent with an incomplete picture.

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 schema has zero parameters, and the description appropriately avoids mentioning any, as there is nothing to explain. Since there are no parameters, the baseline score of 4 applies.

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 begins with the verb 'Returns' and specifies the resource as 'diagnostic signatures that are looping in this server session.' This clearly distinguishes the tool from siblings like ping or check_files, which focus on other aspects, making the purpose unambiguous even without explicit differentiation.

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 lacks any guidance on when to use this tool or when to prefer alternatives. It does not mention any prerequisites, exclusions, or related tools such as ping or check_project, leaving the agent without routing information.

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