Delimit Sensor Github Migrations

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds meaningful behavioral context: it is read-only via the GitHub API, enforces a per-repo allowlist with the LED-881 confused-deputy guard, refuses non-allowlisted repos, and calls ai.social_target.scan_github_migrations. This goes well beyond the structured annotations.

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 well-organized with scannable sections: a front-loaded purpose sentence, explicit usage guidance, sibling contrast, and side effects. Every section earns its place and adds actionable context without fluff.

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?

Given a high-coverage schema, an output schema, and only two parameters, the description is fully complete. It covers purpose, usage boundaries, sibling differentiation, side effects, allowlist constraints, and internal delegation, so an agent has everything needed to call it correctly.

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 input schema already documents the repos and limit parameters fully. The description mentions scanning target repos and migration signals, but it does not add parameter-level detail beyond what the schema provides. Baseline 3 is appropriate here.

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 states a specific verb, resource, and scope: 'Scan GitHub issues/PRs for migration patterns across target repos.' It further distinguishes itself from sibling tools by name, so an agent can tell it apart from delimit_sensor_github_issue, delimit_github_scan, and delimit_sense without opening schemas.

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 explicitly provides 'When to use' and 'When NOT to use' conditions, including named alternatives such as delimit_sense, delimit_sensor_github_issue, and delimit_github_scan. This gives clear routing guidance and leaves no ambiguity about selection.

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