login_status

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

Description implies a read-only check with no side effects, but lacks details on what happens when not logged in, error conditions, or return behavior. Since no annotations exist, the description carries the full burden but provides only basic transparency.

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?

Description is a single concise sentence front-loading the core purpose with no wasted words.

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?

Tool is simple with no parameters or output schema, but description does not specify the return type (e.g., boolean or status string), leaving room for ambiguity. Agent would benefit from knowing what the output represents.

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?

No parameters, so schema coverage is 100%. Baseline is 4; description adds no extra meaning beyond the empty schema, which is acceptable.

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?

Description clearly states the tool checks login status for image generation, using specific verb and resource. It implicitly distinguishes from sibling tools which generate content.

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?

No guidance on when to use this tool versus alternatives. Although it is implicitly a precondition for image generation, the description does not explicitly state that it should be used before calling generate_image or other tools.

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