twin_context

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

No annotations are provided. The description implies a read operation (returning data) but does not disclose side effects, permissions needed, or behavior under different inputs (e.g., what happens with invalid task?). It lacks any behavioral context beyond the opaque list of returned elements.

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 a single short sentence, which is very concise. However, it could be more structured by front-loading the core purpose and then adding parameter or usage details. The conciseness is positive, but the lack of additional information is a trade-off.

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 no annotations, no output schema, and 4 parameters with no description coverage, the description is woefully incomplete. It fails to explain what the tool actually does, how parameters affect results, or what the response looks like. A tool with this complexity requires a much richer description to be usable.

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 input schema has 4 parameters (task, limit, include_source, min_score) with 0% description coverage. The tool description does not explain these parameters at all, leaving the agent to rely solely on the schema titles and defaults. Since the description does not add any semantic value, the score is minimal.

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 the tool returns 'task COV + top twins + seam + rubric' for implementation guidance. The verb 'Return' is clear, but the resource identifiers are jargon (COV, twins, seam) that may not be understood without domain knowledge. It distinguishes somewhat from siblings like 'behavioral_twins' and 'high_coupling_seams' by combining these concepts, but the differentiation is implicit.

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?

No guidance on when to use this tool versus alternatives. Sibling tools like 'behavioral_twins', 'high_coupling_seams', and 'task_fingerprint' have overlapping themes, but no comparative context is provided. The description does not mention prerequisites, limitations, or exclusions.

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