roboflow_api_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys the core purpose (checking connectivity and key validity) but does not disclose what the tool returns, whether it has side effects, or how errors are reported. This is acceptable for a simple status check but leaves gaps.

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 two short sentences, front-loaded with the action and purpose. Every word earns its place, with no redundancy or filler. It is ideally sized for quick comprehension.

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 zero-parameter, no-output-schema tool, the description is fairly complete: it states what the tool does and when to use it. However, it could be slightly enhanced by mentioning the expected response format (e.g., success/failure status) to fully prepare the agent, but this is not critical given the tool's simplicity.

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 input schema is empty (0 parameters), so schema coverage is 100%. The description adds contextual meaning by indicating the tool's functionality (connectivity and key validity), which helps the agent understand that no parameters are needed and that the tool performs a configuration check. The baseline for 0 params is 4, and the description reinforces this without adding unnecessary detail.

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 'Check' and clearly identifies the resource: 'Roboflow API connectivity and key validity'. This distinguishes the tool from sibling tools like search, project list, and inference run, which serve different purposes.

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 explicitly states when to use this tool: 'Use as a first call to verify setup.' This provides clear contextual guidance and implies that it should be used before other Roboflow operations, effectively differentiating it from alternative actions.

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