nest_intake_flags

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

With no annotations available, the description carries the full burden of behavioral disclosure. It adds valuable context: the classifier never rewrites its own rules and a human must ratify the delta, signaling a read-only review action. It does not describe return shape or pagination, but the core behavioral contract is clear.

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 tightly written sentences with the action front-loaded. The parenthetical about CORRECTION_FLAG_THRESHOLD and the human-ratification caveat add meaningful context without unnecessary verbosity.

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 list tool with one parameter and no output schema, the description covers the meaning of the flags, the trigger condition, and the human-in-the-loop workflow. It could benefit from a note about how app_id scopes the query and what fields the list returns, but it is sufficiently complete for basic tool selection and invocation.

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 only parameter, app_id, is not explained in the description at all, and schema description coverage is 0%. The agent receives no help understanding how app_id scopes the flags or what values are valid, beyond the bare type/name provided by the schema. The description fails to compensate for the low schema coverage.

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 the specific verb 'List' plus the resource 'open rule-delta flags' and explains the condition under which flags are created (classifier got wrong often enough, threshold overrides). This clearly distinguishes it from siblings like nest_intake_scan or friction_flags_list by focusing on rule-delta proposals awaiting human ratification.

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 the tool is for reviewing rule-delta proposals before human ratification, but it does not explicitly state when to use this tool instead of nest_intake_scan, nest_intake_queue, or friction_flags_list, nor does it mention when it should not be used. The use case is inferable but not spelled out.

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