darklens_get_fair_pattern_guide

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

No annotations are provided, so the description carries the behavioral burden. The verb 'Retrieve' implies a read-only lookup and the description names the returned content, but it does not state authentication requirements, rate limits, error behavior, or output format.

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?

It is a single front-loaded sentence with no filler. Every clause contributes to identifying the tool’s purpose and returned content.

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 low-complexity, one-parameter lookup tool with no output schema, the description adequately states what is returned: rules, citations, and compliant alternatives. It could be stronger by noting output format or category handling, but the core context is present.

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?

Schema description coverage is 100%, so the parameter is already well documented with example categories. The description reinforces that the tool works for specific deceptive design categories but does not add syntax, valid values, or behavior beyond the schema.

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, 'Retrieve', and clearly identifies the resource: regulatory compliance rules, legal citations, and compliant UI/UX alternatives for deceptive design categories. It is readily distinguishable from the audit siblings because it is a reference-guide lookup rather than an auditing operation.

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 implies usage by saying it is 'for specific deceptive design categories', which tells the agent when the tool applies. However, it does not explicitly say when to choose this over the sibling audit tools or what workflow it fits into.

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