get_sunset_profile

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

Discloses a known upstream bug and implies a read-only operation via 'print'. Without annotations, the description adequately covers the tool's behavior for its simple purpose.

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?

Two sentences front-load the core purpose and add a crucial bug context without waste. Every sentence is necessary.

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?

Lacks description of the output format (e.g., what the profile looks like). While the name implies a simple text output, explicit mention of return value would improve completeness.

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 exist, and schema coverage is 100%. The description adds no parameter info, but none is needed, so the baseline 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 uses 'Print hyprsunset's currently active time-based profile' with a specific verb and resource, clearly distinguishing it from sibling tools like set_sunset_gamma and reset_sunset.

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?

Provides a note about a known bug, guiding the agent on error handling and setting expectations. Lacks explicit when-not-to-use or alternative directions but is sufficient for a simple query tool.

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