kira_consent

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

Description discloses behavior for each level, including that 'off' still writes a local log and 'full' uploads sanitized notes. Annotations (idempotentHint=true) are consistent; no contradiction adds extra context about persistence and redaction.

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?

Five sentences efficiently cover purpose, levels, query behavior, and reference to external doc. Front-loaded and 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?

For a simple set/query tool with one parameter and no output schema, the description covers all key behaviors (query, set, levels) and points to PRIVACY.md for wire format, making it complete.

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 has 100% coverage with enum and description for the single parameter 'level'. Description adds meaning by detailing the data sent at each level, going beyond the schema's brief description.

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 sets telemetry consent level for kira_report with three distinct levels explained. It uniquely addresses consent among sibling tools (kira_get, kira_lookup, etc.).

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?

States when to query (no arguments) and refers to PRIVACY.md for details. Does not explicitly exclude usage scenarios or list alternatives, but the context is clear.

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